fix(deps): bump urql from 2.2.2 to 4.0.0

[dependabot]

Bumps urql from 2.2.2 to 4.0.0.

Release notes

Sourced from urql's releases.

next-urql@4.0.0

Major Changes

• Goodbye IE11! 👋 This major release removes support for IE11. All code that is shipped will be transpiled much less and will not be ES5-compatible anymore, by @​kitten (See #2504)

Patch Changes

• Updated dependencies (See #2504, #2607, and #2504)
  • urql@3.0.0

@​urql/core@​4.0.0

Major Changes

• Remove defaultExchanges from @urql/core and make exchanges a required property on Client construction. In doing so we make the urql package more tree-shakeable as the three default exchanges are in no code paths meaning they can be removed if not used. A migration would look as follows if you are currently creating a client without exchanges

  import { createClient, cacheExchange, fetchExchange } from '@urql/core';
  const client = createClient({
  url: '',
  exchanges: [cacheExchange, fetchExchange],
  });

  Submitted by @​JoviDeCroock (See #3033)

• Update subscriptionExchange to receive FetchBody instead. In the usual usage of subscriptionExchange (for instance with graphql-ws) you can expect no breaking changes. However, the key and extensions field has been removed and instead the forwardSubscription function receives the full Operation as a second argument Submitted by @​kitten (See #3054)

• Remove dependence on graphql package and replace it with @0no-co/graphql.web, which reduces the default bundlesize impact of urql packages to a minimum. All types should remain compatible, even if you use graphql elsewhere in your app, and if other dependencies are using graphql you may alias it to graphql-web-lite Submitted by @​kitten (See #3097)

• Update OperationResult.hasNext and OperationResult.stale to be required fields. If you have a custom exchange creating results, you'll have to add these fields or use the makeResult, mergeResultPatch, or makeErrorResult helpers Submitted by @​kitten (See #3061)

• Remove getOperationName export from @urql/core Submitted by @​kitten (See #3062)

Minor Changes

• Return a new OperationResultSource from all Client methods (which replaces PromisifiedSource on shortcut methods). This allows not only toPromise() to be called, but it can also be used as an awaitable PromiseLike and has a .subscribe(onResult) method aliasing the subscribe utility from wonka Submitted by @​kitten (See #3060)
• Update subscriptionExchange to support incremental results out of the box. If a subscription proactively completes, results are also now updated with hasNext: false Submitted by @​kitten (See #3055)
• Implement text/event-stream response support. This generally adheres to the GraphQL SSE protocol and GraphQL Yoga push responses, and is an alternative to multipart/mixed Submitted by @​kitten (See #3050)
• Implement GraphQL Multipart Request support in @urql/core. This adds the File/Blob upload support to @urql/core, which effectively deprecates @urql/exchange-multipart-fetch Submitted by @​kitten (See #3051)
• Support GraphQLRequest.extensions as spec-extensions input to GraphQL requests Submitted by @​kitten (See #3054)
• Allow subscriptions to be handled by the fetchExchange when fetchSubscriptions is turned on

... (truncated)

Changelog

Sourced from urql's changelog.

4.0.0

Major Changes

• Remove the default Client from Context. Previously, urql kept a legacy default client in its context, with default exchanges and calling an API at /graphql. This has now been removed and you will have to create your own Client if you were relying on this behaviour Submitted by @​JoviDeCroock (See #3033)

Minor Changes

• Allow mutations to update their results in bindings when hasNext: true is set, which indicates deferred or streamed results Submitted by @​kitten (See #3103)

Patch Changes

• ⚠️ Fix source maps included with recently published packages, which lost their sourcesContent, including additional source files, and had incorrect paths in some of them Submitted by @​kitten (See #3053)
• Upgrade to wonka@^6.3.0 Submitted by @​kitten (See #3104)
• Silence "Cannot update a component (%s) while rendering a different component (%s)." warning forcefully Submitted by @​kitten (See #3095)
• Add TSDocs to all urql bindings packages Submitted by @​kitten (See #3079)
• Updated dependencies (See #3101, #3033, #3054, #3053, #3060, #3081, #3039, #3104, #3082, #3097, #3061, #3055, #3085, #3079, #3087, #3059, #3055, #3057, #3050, #3062, #3051, #3043, #3063, #3054, #3102, #3097, #3106, #3058, and #3062)
  • @​urql/core@​4.0.0

3.0.4

Patch Changes

• ⚠️ Fix type utilities turning the variables properties optional when a type from TypedDocumentNode has no Variables or all optional Variables. Previously this would break for wrappers, e.g. in code generators, or when the type didn't quite match what we'd expect Submitted by @​kitten (See #3022)
• Updated dependencies (See #3007, #2962, #3007, #3015, and #3022)
  • @​urql/core@​3.2.0

3.0.3

Patch Changes

• ⚠️ Fix fetching going to false after changing variables in a subscription, by @​JoviDeCroock (See #2667)

3.0.2

Patch Changes

• Update generics for components, by @​JoviDeCroock (See #2663)
• Updated dependencies (See #2665)
  • @​urql/core@​3.0.3

3.0.1

... (truncated)

Commits

• 8ae1c6f Version Packages (#3108)
• 6d2b91e chore: Upgrade to wonka@^6.3.0 (#3104)
• d0d0694 refactor(bindings): Allow hasNext mutation results to update repeatedly (#3103)
• 3600bb6 chore: Bump wonka to ^6.2.6 across all packages (#3099)
• f182601 major(core/graphcache): Remove graphql imports by default (#3097)
• 4ad1967 fix(react-urql): Silence react render phase warning (#3095)
• 47c34c4 docs(packages): Add TSDocs to all remaining packages (#3079)
• d375de2 chore(workspace): Upgrade dependencies (#3068)
• 2fc9842 refactor(core): Refactor hasNext/stale on OperationResult to be required (#3061)
• 40911d2 major(core): remove default exchanges (#3033)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1671.