-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 devdependencies (major) #11959
base: main
Are you sure you want to change the base?
Conversation
|
size-limit report 📦
|
6a9ee40
to
1cd58da
Compare
db469ce
to
841baac
Compare
13e39fe
to
0bffc03
Compare
d682bff
to
4574e96
Compare
fa663e1
to
c93c917
Compare
c93c917
to
fa0342b
Compare
commit: |
0f5d3cd
to
61c9d08
Compare
61c9d08
to
ed97593
Compare
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: 92260e0434ff3f750cd54af0 |
46d4c24
to
dc90980
Compare
97c6cd3
to
eddd2d0
Compare
eddd2d0
to
a65ba6d
Compare
0e9112e
to
cd583bb
Compare
e3d6ae4
to
91f58cc
Compare
112dc8f
to
b15d7e2
Compare
a7ce63e
to
bf520d4
Compare
bf520d4
to
c43a491
Compare
b72bab6
to
06b246c
Compare
06b246c
to
50fd61f
Compare
a6ce1d5
to
83690ec
Compare
83690ec
to
f3c6881
Compare
f3c6881
to
f40d9c0
Compare
✅ Deploy Preview for apollo-client-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This PR contains the following updates:
14.1.24
->18.2.5
7.0.20220408
->9.0.20240710
9.11.0
->12.2.0
5.16.0
->6.0.2
0.16.1
->17.1.2
4.0.13
->5.0.0
5.0.9
->6.0.1
Release Notes
bjornstar/blob-polyfill (blob-polyfill)
v9.0.20240710
Compare Source
master
branch build status (@bjornstar)@sindresorhus/is
,eslint
, &mocha
(@bjornstar)eslint.config.mjs
for eslint@9 (@bjornstar)v8.0.20240630
Compare Source
isPolyfill
property to the polyfilled versions so we can differentiate them (@bjornstar)wheresrhys/fetch-mock (fetch-mock)
v12.2.0
Compare Source
Features
v12.1.0
Compare Source
Features
v12.0.2
Compare Source
Bug Fixes
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
⚠ BREAKING CHANGES
Features
v11.1.5
Compare Source
Bug Fixes
v11.1.4
Compare Source
Documentation Changes
v11.1.3
Compare Source
Bug Fixes
v11.1.1
Compare Source
Bug Fixes
v11.1.0
Compare Source
Features
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
⚠ BREAKING CHANGES
Bug Fixes
v10.1.1
Compare Source
Bug Fixes
v10.1.0
Compare Source
Features
Bug Fixes
v10.0.8
Compare Source
Miscellaneous
v10.0.7
: Make type definitions compatible with ESM and CommonJsCompare Source
v10.0.6
: Fix type definitionsCompare Source
v10.0.5
: Fix exportsCompare Source
v10.0.4
: Simple API for naming routesCompare Source
e.g.
.mock('/path', 200, 'my-name')
v10.0.3
: Remove custom aborterror implementationCompare Source
v10.0.2
: Support matching data URLsCompare Source
v10.0.1
: Small fixes to typesCompare Source
v10.0.0
: ESM and native fetchCompare Source
A major rewrite to use ESM modules and default to using native fetch in all environments
Other than that the API remains unchanged
enisdenjo/graphql-ws (graphql-ws)
v6.0.2
Compare Source
Patch Changes
6b180e8
Thanks @pleunv! - FormattedExecutionResult errors field returns GraphQLFormattedErrorv6.0.1
Compare Source
Patch Changes
#618
6be34c7
Thanks @enisdenjo! - Remove exports for CommonJS for Deno exports in package.jsonDeno supports ECMAScript modules exclusively.
#618
6be34c7
Thanks @enisdenjo! - Define exports for CommonJS TypeScript definitions in package.jsonv6.0.0
Compare Source
Major Changes
b668b30
Thanks @enisdenjo! - @fastify/websocket WebSocket in the context extra has been renamed fromconnection
tosocket
Migrating from v5 to v6
#613
3f11aba
Thanks @enisdenjo! - Drop support forws
v7ws
v7 has been deprecated. Please upgrade and use v8.#613
3f11aba
Thanks @enisdenjo! - Drop support for deprecatedfastify-websocket
fastify-websocket
has been deprecated since v4.3.0.. Please upgrade and use@fastify/websocket
.#613
3f11aba
Thanks @enisdenjo! - The/lib/
part from imports has been removed, for examplegraphql-ws/lib/use/ws
becomesgraphql-ws/use/ws
Migrating from v5 to v6
Simply remove the
/lib/
part from your graphql-ws imports that use a handler.ws
uWebSockets.js
@fastify/websocket
Bun
Deno
#613
3f11aba
Thanks @enisdenjo! -ErrorMessage
uses andonError
returnsGraphQLFormattedError
(instead ofGraphQLError
)Thanks @benjie for working on this in #599
#613
3f11aba
Thanks @enisdenjo! - Least supported Node version is v20Node v10 has been deprecated for years now. There is no reason to support it. Bumping the engine to the current LTS (v20) also allows the code to be leaner and use less polyfills.
#613
3f11aba
Thanks @enisdenjo! - Least supportedgraphql
peer dependency is ^15.10.1 and ^16Users are advised to use the latest of
graphql
because of various improvements in performance and security.#613
3f11aba
Thanks @enisdenjo! -NextMessage
uses andonNext
returnsFormattedExecutionResult
(instead ofExecutionResult
)#613
3f11aba
Thanks @enisdenjo! -schema
,context
,onSubscribe
,onOperation
,onError
,onNext
andonComplete
hooks don't have the full accompanying message anymore, only the ID and the relevant part from the messageThere is really no need to pass the full
SubscribeMessage
to theonSubscribe
hook. The only relevant parts from the message are theid
and thepayload
, thetype
is useless since the hook inherently has it (onNext
isnext
type,onError
iserror
type, etc).The actual techincal reason for not having the full message is to avoid serialising results and errors twice. Both
onNext
andonError
allow the user to augment the result and return it to be used instead.onNext
originally had theNextMessage
argument which already has theFormattedExecutionResult
, andonError
originally had theErrorMessage
argument which already has theGraphQLFormattedError
, and they both also returnedFormattedExecutionResult
andGraphQLFormattedError
respectivelly - meaning, if the user serialised the results - the serialisation would happen twice.Additionally, the
onOperation
,onError
,onNext
andonComplete
now have thepayload
which is theSubscribeMessage.payload
(SubscribePayload
) for easier access to the original query as well as execution params extensions.Migrating from v5 to v6
schema
context
onSubscribe
onOperation
The
SubscribeMessage.payload
is not useful here at all, thepayload
has been parsed to ready-to-use graphql execution args and should be used instead.onError
The
ErrorMessage.payload
(GraphQLFormattedError[]
) is not useful here at all, the user has access toGraphQLError[]
that are true instances of the error containing object references tooriginalError
s and other properties. The user can always convert and returnGraphQLFormattedError[]
by using the.toJSON()
method.onNext
The
NextMessage.payload
(FormattedExecutionResult
) is not useful here at all, the user has access toExecutionResult
that contains actual object references to error instances. The user can always convert and returnFormattedExecutionResult
by serialising the errors withGraphQLError.toJSON()
method.onComplete
#613
3f11aba
Thanks @enisdenjo! - Errors thrown from subscription iterables will be caught and reported through theErrorMessage
Compared to the behaviour before, which terminated the whole WebSocket connection - those errors are now gracefully reported and terminate only the specific subscription that threw the error.
There's been an editorial change in the GraphQL Spec suggesting this being the correct approach.
Also, if you'd like to get involved and ideally drop your opinion about whether iterable errors should be reported as errors or
ExecutionResult
s witherrors
field set, please read more here.Migrating from v5 to v6
If you had used the suggested "ws server usage with custom subscribe method that gracefully handles thrown errors" recipe, you can simply remove it since this behaviour is now baked in.
3f11aba
Thanks @enisdenjo! - Remove deprecatedisMessage
, usevalidateMessage
insteadMigrating from v5 to v6
Replace all ocurrances of
isMessage
withvalidateMessage
. Note thatvalidateMessage
throws if the message is not valid, compared withisMessage
that simply returned true/false.3f11aba
Thanks @enisdenjo! - Removed deprecatedisFatalConnectionProblem
, useshouldRetry
insteadMigrating from v5 to v6
Replace all ocurrances of
isFatalConnectionProblem
withshouldRetry
. Note that the result is inverted, where you returnedfalse
inisFatalConnectionProblem
you should returntrue
inshouldRetry
.Minor Changes
#613
3f11aba
Thanks @enisdenjo! - Client is truly zero-dependency, not even a peer dependency ongraphql
In non-browser environments, you can use only the client and not even depend on
graphql
by importing fromgraphql-ws/client
.Note that, in browser envirments (and of course having your bundler use the
browser
package.json field), you don't have to import fromgraphql-ws/client
- simply importing fromgraphql-ws
will only have thecreateClient
available.#615
29dd26a
Thanks @enisdenjo! - Define optional peer dependencies and least supported versionsUsing the
peerDependencies
in combination withpeerDependenciesMeta
configuration inpackage.json
.v5.16.2
Compare Source
Patch Changes
#611
6a5fde1
Thanks @enisdenjo! - No more workspacesThis version does not contain any code changes.
v5.16.1
Compare Source
Patch Changes
#607
a629ec7
Thanks @enisdenjo! - Release with changesetsThis version does not contain any code changes.
facebook/jscodeshift (jscodeshift)
v17.1.2
Compare Source
Patch Changes
8f60fbf
: Enable async tranformers in test utils.All notable changes to this project will be documented in this file.
v17.1.1
Compare Source
Fixed
temp
dependency properly removed (#638, thanks @trivikr for reporting)v17.1.0
Compare Source
Added
pkg.pr.new
will now be used to build an npm pakage for each commit to the repo, allowing you to more easily test changes or use new features before an official release is cut. (#622, @Aslemammad)Changed
temp
library withtmp
(#633, @r4zendev)Fixed
docs
command frompackage.json
since the new docs are in thewebsite
folder, which has instructions in its README.v17.0.0
Compare Source
We needed to go from v0.x to a major release, and it may as well happen now. jscodeshift has been around for nine years though, so going to v1.0.0 didn't feel quite right. I've instead promoted the minor version number to a major version number, similar to what React did when it went from 0.14 to 15.0.
Fixed
Added
Changed
importAttributes
(#585, @benasher44) anddecoratorAutoAccessors
(#594, @syi0808) pluginsbvaughn/react-error-boundary (react-error-boundary)
v5.0.0
Compare Source
Update
withErrorBoundary
types to be compatible with the latestforwardRef
typesFor more background see PR #211
v4.1.2
Compare Source
v4.1.1
Compare Source
v4.1.0
Compare Source
isaacs/rimraf (rimraf)
v6.0.1
Compare Source
v6.0.0
Compare Source
v5.0.10
Compare Source
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.