Bump urql from 2.0.1 to 2.2.3

[dependabot]

Bumps urql from 2.0.1 to 2.2.3.

Release notes

Sourced from urql's releases.

urql@2.2.3

We urgently recommend all users of the React bindings to upgrade to this patch!

Please don't forget to deduplicate your installed version of @urql/core after you upgrade.

Patch Changes

• ⚠️ Fix missing React updates after an incoming response that schedules a mount. We now prevent dispatched operations from continuing to flush synchronously when the original source that runs the queue has terminated. This is important for the React bindings, because an update (e.g. setState) may recursively schedule a mount, which then disabled other setState updates from being processed. Previously we assumed that React used a trampoline scheduler for updates, however it appears that setState can recursively start more React work, by @​kitten (See #2556)
• Updated dependencies (See #2556)
  • @​urql/core@​2.6.1

urql@2.2.2

Patch Changes

• ⚠️ Fix Node.js ESM re-export detection for @urql/core in urql package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @​kitten (See #2485)

urql@2.2.1

Patch Changes

• ⚠️ Fix issue where a paused subscription would execute with stale variables, by @​JoviDeCroock (See #2463)

@​urql/core@​2.2.0

Minor Changes

• Add a staleWhileRevalidate option to the ssrExchange, which allows the client to immediately refetch a new result on hydration, which may be used for cached / stale SSR or SSG pages. This is different from using cache-and-network by default (which isn't recommended) as the ssrExchange typically acts like a "replacement fetch request", by @​kitten (See #1852)

Patch Changes

• ⚠️ Fix prevent mangling embedded strings in queries sent using the GET method, by @​JoviDeCroock (See #1851)
• The single-source behavior previously wasn't effective for implementations like React, where the issue presents itself when the state of an operation is first polled. This led to the operation being torn down erroneously. We now ensure that operations started at the same time still use a shared single-source, by @​JoviDeCroock (See #1850)

urql@2.2.0

Minor Changes

• Revert to the previous useQuery implementation, use-sync-external-store seems to be causing some unexpected timing issues, by @​JoviDeCroock (See #2308)

Patch Changes

• Updated dependencies (See #2295)
  • @​urql/core@​2.4.3

@​urql/core@​2.1.6

Patch Changes

• Warn for invalid operation passed to query/subscription/mutation, by @​JoviDeCroock (See #1829)

@​urql/core@​2.1.5

Patch Changes

... (truncated)

Changelog

Sourced from urql's changelog.

2.2.3

Patch Changes

• ⚠️ Fix missing React updates after an incoming response that schedules a mount. We now prevent dispatched operations from continuing to flush synchronously when the original source that runs the queue has terminated. This is important for the React bindings, because an update (e.g. setState) may recursively schedule a mount, which then disabled other setState updates from being processed. Previously we assumed that React used a trampoline scheduler for updates, however it appears that setState can recursively start more React work, by @​kitten (See #2556)
• Updated dependencies (See #2556)
  • @​urql/core@​2.6.1

2.2.2

Patch Changes

• ⚠️ Fix Node.js ESM re-export detection for @urql/core in urql package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @​kitten (See #2485)

2.2.1

Patch Changes

• ⚠️ Fix issue where a paused subscription would execute with stale variables, by @​JoviDeCroock (See #2463)

2.2.0

Minor Changes

• Revert to the previous useQuery implementation, use-sync-external-store seems to be causing some unexpected timing issues, by @​JoviDeCroock (See #2308)

Patch Changes

• Updated dependencies (See #2295)
  • @​urql/core@​2.4.3

2.1.3

Patch Changes

• ⚠️ fix diff data correctly for the next state computing, this avoids having UI-flashes due to undefined data, by @​JoviDeCroock (See #2238)
• ⚠️ fix issue where the cache infinitely loops, by @​JoviDeCroock (See #2237)

2.1.2

Patch Changes

• Update useQuery implementation to avoid an aborted render on initial mount. We abort a render-on-update once when the state needs to be updated according to the OperationResult source we need to listen to and execute. However, we can avoid this on the initial mount as we've done in a prior version. This fix does not change any of the current behaviour, but simply avoids the confusing state transition on mount, by @​kitten (See #2227)
• Updated dependencies (See #2228)
  • @​urql/core@​2.4.1

2.1.1

Patch Changes

... (truncated)

Commits

• cf43912 Version Packages (#2557)
• 3217333 fix(react): Prevent the operation queue from being flushed during synchronous...
• 054eeac Version Packages (#2487)
• 58f887c Version Packages (#2464)
• 64163c6 fix(react): execute subscriptions with latest vars (#2463)
• 72882d3 chore(react): create a Suspense E2E test suite w/ cypress (#2341)
• 8e92357 Version Packages (#2301)
• 85d5a37 fix(urql): call cache.get inside of snapshots (#2308)
• f9c5765 Version Packages (#2241)
• 393912e (react) - diff data correctly for the next state computing (#2238)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by npm-urql, a new releaser for urql since your current version.

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)