urql

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)
• 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]

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

• ⚠️ Fix use context of the reexecuting operation, by @JoviDeCroock (See #2104)

Patch Changes

• ⚠️ Fix operations sometimes not being executed after a retry is supposed to be triggered, due to a setTimeout reordering issue when the timer isn't as predictable as it should be, by @kitten (See #2124)

Patch Changes

• ⚠️ Fix Crypto API support for Web Workers and Node Crypto in ESM mode. Previously, when Node Crypto was required in Node ESM mode it would result in an error instead, since we didn't try a dynamic import fallback, by @kitten (See #2123)

Patch Changes

• ⚠️ Fix bail when the getInitialProps call indicates we've finished the response, by @JoviDeCroock (See #2101)

Patch Changes

• ⚠️ Fix issue where maskTypename would ignore array shapes, by @JoviDeCroock (See #2074)

Minor Changes

• Add subscription support, by @Tigge (See #2061)

Patch Changes

• Updated dependencies (See #2074)
  • @urql/[email protected]

Minor Changes

• Support forwarding the getLayout function from pages, by @JoviDeCroock (See #2065)

Minor Changes

• Provide the client as a ref so it can observe changes. This change is potentially breaking for
  anyone using the useClient import as it will now return a Ref<Client> rather than a Client, by @JoviDeCroock (See #2047)

Patch Changes

• Updated dependencies (See #2027 and #1998)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix initialize operationStore with fetching: false, the invocation of query or any other operation will mark it as true
  when deemed appropriate, by @JoviDeCroock (See #2048)
• Updated dependencies (See #2027 and #1998)
  • @urql/[email protected]