-
-
Notifications
You must be signed in to change notification settings - Fork 816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #5112
Conversation
🦋 Changeset detectedLatest commit: 5132b15 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
075fdad
to
5f3899f
Compare
05bda64
to
5a1e764
Compare
9782290
to
a34952a
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
✅ Benchmark Results
|
🚀 Snapshot Release (
|
Package | Version | Info |
---|---|---|
@graphql-tools/batch-delegate |
8.4.24-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/delegate |
9.0.30-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor |
0.0.16-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-graphql-ws |
0.0.13-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-legacy-ws |
0.0.10-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-urql-exchange |
0.0.9-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/links |
8.3.34-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/prisma-loader |
7.2.67-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/url-loader |
7.17.15-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitch |
8.7.47-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/stitching-directives |
2.3.33-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/wrap |
9.4.1-alpha-20230406062823-5132b15c |
npm ↗︎ unpkg ↗︎ |
💻 Website PreviewThe latest changes are available as preview in: https://753f84d0.graphql-tools.pages.dev |
This PR contains the following updates:
3.7.10
->3.7.11
2.3.3
->2.4.1
7.21.0
->7.21.4
7.21.2
->7.21.4
7.20.2
->7.21.4
7.21.2
->7.21.4
7.21.2
->7.21.4
3.1.2
->3.2.0
1.7.2
->1.8.0
29.4.0
->29.5.0
4.0.2
->4.0.5
1.0.33
->1.0.34
4.14.191
->4.14.192
18.14.6
->18.15.11
18.0.28
->18.0.33
5.28.0
->5.28.1
8.5.3
->8.5.4
0.8.2
->0.8.4
16.0.0
->16.0.3
0.17.0
->0.17.15
8.35.0
->8.37.0
8.7.0
->8.8.0
15.6.1
->15.7.0
5.0.0
->5.2.0
1.20.1
->1.21.3
2.1.0
->2.1.1
5.12.0
->5.12.1
3.7.2
->3.8.0
4.11.4
->4.13.1
1.0.1
->1.0.2
13.1.2
->13.2.0
2.6.7
->2.6.9
2.8.4
->2.8.7
19.7.3
->19.8.3
3.55.1
->3.58.0
0.6.3
->0.6.11
29.0.5
->29.1.0
5.76.0
->5.78.0
8.12.1
->8.13.0
Release Notes
apollographql/apollo-client
v3.7.11
Compare Source
Patch Changes
#10586
4175af594
Thanks @alessbell! - Improve WebSocket error handling for genericEvent
received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.#10411
152baac34
Thanks @lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.#10592
cdb98ae08
Thanks @alessbell! - Adds support for multipart subscriptions inHttpLink
.#10698
38508a251
Thanks @jerelmiller! - Changes the behavior ofuseLazyQuery
introduced in #10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.Other notable fixes:
useLazyQuery
with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.#10660
364bee98f
Thanks @alessbell! - Upgrades TypeScript to v5. This change is fully backward-compatible and transparent to users.#10597
8fb9d190d
Thanks @phryneas! - Fix a bug where an incoming cache update could prevent future updates from the active link.#10629
02605bb3c
Thanks @phryneas! -useQuery
: delay unsubscribe to fix race conditionsapollographql/federation
v2.4.1
Compare Source
Patch Changes
Fix issues (incorrectly rejected composition and/or subgraph errors) with
@interfaceObject
. Those issues may occur (#2494)either due to some use of
@requires
in an@interfaceObject
type, or when some subgraphS
defines a type that is animplementation of an interface
I
in the supergraph, and there is an@interfaceObject
forI
in another subgraph,but
S
does not itself definesI
.Fix handling of aliases and variables in introspection queries. (#2506)
Start building packages with TS 5.x, which should have no effect on consumers (#2480)
Improves reuse of named fragments in subgraph fetches. When a question has named fragments, the code tries to reuse (#2497)
those fragment in subgraph fetches is those can apply (so when the fragment is fully queried in a single subgraph fetch).
However, the existing was only able to reuse those fragment in a small subset of cases. This change makes it much more
likely that if a fragment can be reused, it will be.
Updated dependencies [
450b9578
,afde3158
,eafebc3c
,01fe3f83
]:v2.4.0
Compare Source
Minor Changes
This change introduces a configurable query plan cache. This option allows (#2385)
developers to provide their own query plan cache like so:
The current default implementation is effectively as follows:
TypeScript users should implement the
QueryPlanCache
type which is nowexported by
@apollo/query-planner
:Adds debug/testing query planner options (
debug.bypassPlannerForSingleSubgraph
) to bypass the query planning (#2441)process for federated supergraph having only a single subgraph. The option is disabled by default, is not recommended
for production, and is not supported (it may be removed later). It is meant for debugging/testing purposes.
Patch Changes
Refactor the internal implementation of selection sets used by the query planner to decrease the code complexity and (#2387)
improve query plan generation performance in many cases.
Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#2449)
Updated dependencies [
260c357c
,7bc0f8e8
,d4426ff9
,a9385bdb
,1a555d98
,ade7ceb8
,09382e74
,cab383b2
]:v2.3.5
Compare Source
Patch Changes
09382e74
]:v2.3.4
Compare Source
Patch Changes
Handle defaulted variables correctly during post-processing. (#2443)
Users who tried to use built-in conditional directives (skip/include) with defaulted variables and no variable provided would encounter an error thrown by operation post-processing saying that the variables weren't provided. The defaulted values went unaccounted for, so the operation would validate but then fail an assertion while resolving the conditional.
With this change, defaulted variable values are now collected and provided to post-processing (with defaults being overwritten by variables that are actually provided).
Updated dependencies [
6e2d24b5
]:babel/babel (@babel/core)
v7.21.4
Compare Source
🐛 Bug Fix
babel-core
,babel-helper-module-imports
,babel-preset-typescript
import/export
in.cts
files (@liuxingbaoyu)babel-generator
💅 Polish
babel-helper-create-class-features-plugin
,babel-plugin-proposal-class-properties
,babel-plugin-transform-typescript
,babel-traverse
🏠 Internal
babel-parser
lookaheadInLineCharCode
(@JLHwung)babel-code-frame
,babel-highlight
v7.21.3
Compare Source
👓 Spec Compliance
babel-parser
🐛 Bug Fix
babel-parser
babel-plugin-transform-typescript
var
decls generated byimport ... =
TS transform (@amoeller)export { type foo }
as type-only usage (@magic-akari)💅 Polish
babel-traverse
,babel-types
@babel
package (@nicolo-ribaudo)babel-generator
jsonCompatibleStrings
deprecation (@liuxingbaoyu)🏠 Internal
🔬 Output optimization
babel-plugin-transform-typescript
,babel-preset-typescript
babel/babel (@babel/parser)
v7.21.4
Compare Source
v7.21.4 (2023-03-31)
🐛 Bug Fix
babel-core
,babel-helper-module-imports
,babel-preset-typescript
import/export
in.cts
files (@liuxingbaoyu)babel-generator
💅 Polish
babel-helper-create-class-features-plugin
,babel-plugin-proposal-class-properties
,babel-plugin-transform-typescript
,babel-traverse
🏠 Internal
babel-parser
lookaheadInLineCharCode
(@JLHwung)babel-code-frame
,babel-highlight
Committers: 6
v7.21.3
Compare Source
v7.21.3 (2023-03-14)
Thanks @amoeller, @Harpica, and @nzakas for your first PRs!
👓 Spec Compliance
babel-parser
🐛 Bug Fix
babel-parser
babel-plugin-transform-typescript
var
decls generated byimport ... =
TS transform (@amoeller)export { type foo }
as type-only usage (@magic-akari)💅 Polish
babel-traverse
,babel-types
@babel
package (@nicolo-ribaudo)babel-generator
jsonCompatibleStrings
deprecation (@liuxingbaoyu)🏠 Internal
🔬 Output optimization
babel-plugin-transform-typescript
,babel-preset-typescript
Committers: 8
dotansimha/graphql-typed-document-node
v3.2.0
Compare Source
dotansimha/graphql-yoga (@graphql-yoga/plugin-defer-stream)
v1.8.0
Compare Source
Bug Fixes
Features
v1.7.3
Compare Source
ardatan/whatwg-node
v0.8.4
Compare Source
Patch Changes
207ee1d
Thanks @ardatan! - Detect Deno if the module is imported via 'npm:'
or any other Node compatibility method
v0.8.3
Compare Source
Patch Changes
bf585a3
Thanks @ardatan! - Support iterable Fetch API methods
Updated dependencies
[
9f242f8
,bf585a3
]:motdotla/dotenv
v16.0.3
Compare Source
Changed
v16.0.2
Compare Source
Added
env-options.js
andcli-options.js
in package.json for use with downstream dotenv-expand modulev16.0.1
Compare Source
Changed
evanw/esbuild
v0.17.15
Compare Source
Allow keywords as type parameter names in mapped types (#3033)
TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:
Add annotations for re-exported modules in node (#2486, #3029)
Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.
To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form
0 && (module.exports = { ... })
and comes at the end of the file (0 && expr
meansexpr
is never evaluated).Previously esbuild didn't do this for modules re-exported using the
export * from
syntax. Annotations for these re-exports will now be added starting with this release:Note that you need to specify both
--format=cjs
and--platform=node
to get these node-specific annotations.Avoid printing an unnecessary space in between a number and a
.
(#3026)JavaScript typically requires a space in between a number token and a
.
token to avoid the.
being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases:Fix server-sent events with live reload when writing to the file system root (#3027)
This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when
outdir
was the file system root, such as/
. This happened because/
is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling.v0.17.14
Compare Source
Allow the TypeScript 5.0
const
modifier in object type declarations (#3021)The new TypeScript 5.0
const
modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:Implement preliminary lowering for CSS nesting (#1945)
Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!
This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the
:is()
pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support:is()
(e.g. Chrome 88+). You'll need to set esbuild's [target
]Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.