Bump urql from 1.11.6 to 2.1.3 in /packages/core

[dependabot]

Bumps urql from 1.11.6 to 2.1.3.

Release notes

Sourced from urql's releases.

@​urql/core@​2.1.3

Patch Changes

• Treat empty variables the same as no variables in @urql/core's createRequest, by @​kitten (See #1695)

urql@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)

@​urql/core@​2.1.2

Patch Changes

• ⚠️ Fix a condition under which the Client would hang when a query is started and consumed with toPromise(), by @​kitten (See #1634)
• Refactor Client to hide some implementation details and to reduce size, by @​kitten (See #1638)

urql@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

@​urql/core@​2.1.1

Patch Changes

• ⚠️ Fix a regression in @urql/core@2.1.1 that prevented concurrent operations from being dispatched with differing request policies, which for instance prevented the explicit executeQuery calls on bindings to fail, by @​kitten (See #1626)

urql@2.1.1

Patch Changes

• pin version for use-sync-external-store, by @​JoviDeCroock (See #2223)

@​urql/core@​2.1.0

Minor Changes

• With the "single-source behavior" the Client will now also avoid executing an operation if it's already active, has a previous result available, and is either run with the cache-first or cache-only request policies. This is similar to a "short circuiting" behavior, where unnecessary work is avoided by not issuing more operations into the exchange pipeline than expected, by @​kitten (See #1600)
• Add consistent "single-source behavior" which makes the Client more forgiving when duplicate sources are used, which previously made it difficult to use the same operation across an app together with cache-and-network; This was a rare use-case, and it isn't recommended to overfetch data across an app, however, the new Client implementation of shared sources ensures that when an operation is active that the Client distributes the last known result for the active operation to any new usages of it (which is called “replaying stale results”) (See #1515)

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• ⚠️ Fix inconsistency in generating keys for DocumentNodes, especially when using GraphQL Code Generator, which could cause SSR serialization to fail, by @​zenflow (See #1509)

... (truncated)

Changelog

Sourced from urql's changelog.

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

• pin version for use-sync-external-store, by @​JoviDeCroock (See #2223)

2.1.0

Minor Changes

• Leverage the new use-sync-external-store package and useSyncExternalStore hook in useQuery implementation to bring the state synchronisation in React in line with React v18. While the current implementation works already with React Suspense and React Concurrent this will reduce the maintenance burden of our implementation and ensure certain guarantees so that React doesn't break us, by @​JoviDeCroock (See #2164)

Patch Changes

• ⚠️ Fix useMutation not working correctly with React 18, by @​Dremora (See #2158)
• Updated dependencies (See #2189, #2153, #2210, and #2198)
  • @​urql/core@​2.4.0

2.0.6

Patch Changes

• Extend peer dependency range of graphql to include ^16.0.0. As always when upgrading across many packages of urql, especially including @urql/core we recommend you to deduplicate dependencies after upgrading, using npm dedupe or npx yarn-deduplicate, by @​kitten (See #2133)
• Updated dependencies (See #2133)
  • @​urql/core@​2.3.6

2.0.5

Patch Changes

• ⚠️ Fix issue where a paused query would not behave correctly when calling executeQuery, this scenario occured when the query has variables, there would be cases where on the first call it would think that the dependencies had changed (previous request vs current request) which made the source reset to null, by @​JoviDeCroock (See #1982)
• Updated dependencies (See #1944)
  • @​urql/core@​2.3.2

... (truncated)

Commits

• f9c5765 Version Packages (#2241)
• 393912e (react) - diff data correctly for the next state computing (#2238)
• d3634b1 (react) - fix issue where the cache infinitely loops (#2237)
• 1ec08fa Version Packages (#2229)
• b79986a (react) - Update initial state to not require abort on mount (#2227)
• 481bf43 Version Packages (#2224)
• 4795a3a pin correct version (#2223)
• 4d4827c Version Packages (#2154)
• ac2ddad (react) - leverage the new use-sync-external-store package (#2164)
• 771607e Ensure useMutation is compatible with React 18 (#2158)
• 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)

[dependabot]

Superseded by #1079.