urql

Patch Changes

• ⚠️ Fix: add the ENTRIES_STORE_NAME to the clear transaction, by @JoviDeCroock (See #1685)
• Updated dependencies (See #1695)
  • @urql/[email protected]

Patch Changes

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

Patch Changes

• Loosen type constraint on ScalarObject to account for custom scalar deserialization like Date for DateTimes, by @kitten (See #1648)
• Loosen the typing constraint on the cacheExchange generic, by @JoviDeCroock (See #1675)

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)

Patch Changes

• ⚠️ Fix TTL being updated to a newer timestamp when a cached result comes in, and prevent TTL from being deleted on our React binding's cache probes. Instead we now never delete the TTL and update it on incoming cache miss results, by @kitten (See #1641)
• Updated dependencies (See #1634 and #1638)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix an edge-case for which an introspection query during runtime could fail when schema-awareness was enabled in Graphcache, since built-in types weren't recognised as existent, by @kitten (See #1631)

Patch Changes

• ⚠️ Fix a regression in @urql/[email protected] 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)

Patch Changes

• ⚠️ Fix a stray operationName deprecation warning in @urql/exchange-graphcache's exchange logic, which adds the meta.cacheOutcome field to the operation's context, by @kitten (See #1103)

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies
  • [email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by @kitten (See #1097)
• Updated dependencies (See #1097)
  • @urql/[email protected]

This version of @urql/core renames Operation.operationName to Operation.kind. For now the old
property is merely deprecated and will issue a warning if it's used directly. That said, all
exchanges that are released today also need this new version of @urql/core@>=1.14.0, so if you
upgrade to any of the following packages, you will also need to upgrade @urql/core. If you upgrade
and see the deprecation warning, check whether all following exchanges have been upgraded:

• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]
• @urql/[email protected]

Edit: Some of these packages have already been bumped by another patch version. Please just double check that you're bumping to the newest version, if possible.**

Once you've upgraded @urql/core please also ensure that your package manager hasn't accidentally
duplicated the @urql/core package. If you're using npm you can do so by running npm dedupe,
and if you use yarn you can do so by running yarn-deduplicate.

If you have a custom exchange, you can mute the deprecation warning by using Operation.kind rather
than Operation.operationName. If these exchanges are copying or altering operations by spreading
them this will also trigger the warning, which you can fix by using the new makeOperation helper
function.

Minor Changes

• Deprecate the Operation.operationName property in favor of Operation.kind. This name was
  previously confusing as operationName was effectively referring to two different things. You can
  safely upgrade to this new version, however to mute all deprecation warnings you will have to
  upgrade all urql packages you use. If you have custom exchanges that spread operations, please
  use the new makeOperation helper
  function instead, by @bkonkle (See #1045)

Patch Changes

• Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)

Minor Changes

• Update next-urql types to be free-standing and not depend on the types from the next packages, by @kitten (See #1095)

Patch Changes

• Updated dependencies (See #1045)
  • [email protected]

Patch Changes

• Deprecate the Operation.operationName property in favor of Operation.kind. This name was
  previously confusing as operationName was effectively referring to two different things. You can
  safely upgrade to this new version, however to mute all deprecation warnings you will have to
  upgrade all urql packages you use. If you have custom exchanges that spread operations, please
  use the new makeOperation helper
  function instead, by @bkonkle (See #1045)
• Updated dependencies (See #1094 and #1045)
  • @urql/[email protected]

Patch Changes

• Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
• Deprecate the Operation.operationName property in favor of Operation.kind. This name was
  previously confusing as operationName was effectively referring to two different things. You can
  safely upgrade to this new version, however to mute all deprecation warnings you will have to
  upgrade all urql packages you use. If you have custom exchanges that spread operations, please
  use the new makeOperation helper
  function instead, by @bkonkle (See #1045)
• Updated dependencies (See #1094 and #1045)
  • @urql/[email protected]