urql

Patch Changes

• Export RetryExchangeOption type from top level export, by @KoltonG (See #2351)
• Updated dependencies (See #2384 and #2386)
  • @urql/[email protected]

Patch Changes

• cut off url when using the GET method at 2048 characters (lowest url-size coming from chromium), by @JoviDeCroock (See #2384)
• ⚠️ Fix issue where a synchronous toPromise() return would not result in the stream tearing down, by @JoviDeCroock (See #2386)

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/[email protected]

Patch Changes

• Prevent ignored characters in GraphQL queries from being replaced inside strings and block strings. Previously we accepted sanitizing strings via regular expressions causing duplicate hashes as acceptable, since it'd only be caused when a string wasn't extracted into variables. This is fixed now however, by @kitten (See #2295)

Patch Changes

• Undo logic to catch errors from incremental fetching and forking the response stream, introduce logic
  to detect results, by @JoviDeCroock (See #2287)

Patch Changes

• ⚠️ Fix import of executeSync rather than execute causing an incompatibility when several .mjs imports and a main import { executeSync } from 'graphql' are causing two different modules to be instantiated, by @kitten (See #2251)

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)

Patch Changes

• ⚠️ Fix mutation operation being used as compared identity and instead add a stand-in comparison, by @kitten (See #2228)

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/[email protected]

Patch Changes

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

Minor Changes

• Allow for repeated mutations that have similar inputs which results in the same key, this is for instance the case with file uploads, by @JoviDeCroock (See #2189)

Patch Changes

• Bump @graphql-typed-document-node/core to 3.1.1 for graphql@16 support, by @JoviDeCroock (See #2153)
• ⚠️ Fix error bubbling, when an error happened in the exchange-pipeline we would treat it as a GraphQL-error, by @JoviDeCroock (See #2210)
• Filter network-only requests from the ssrExchange, this is to enable staleWhileRevalidated queries to successfully dispatch their queries, by @JoviDeCroock (See #2198)

Patch Changes

• ⚠️ Fix issue where the in-memory cache would not be cleared, by @benmechen (See #2222)

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/[email protected]

Patch Changes

• Upgrade modular imports for graphql package, which fixes an issue in @urql/exchange-execute, where graphql@16 files wouldn't resolve the old subscribe import from the correct file, by @kitten (See #2149)

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/[email protected]

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/[email protected]

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/[email protected]

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/[email protected]

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)

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/[email protected]