urql

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]

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

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

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

• 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

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

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)
• Updated dependencies (See #1094 and #1045)
  • @urql/[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]

Minor Changes

• Switch from a focus-event triggering the refetch to a change in page-visbility. This means that interacting with an iframe and then going back to the page won't trigger a refetch, interacting with Devtools won't cause refetches and a bubbled focusEvent won't trigger a refetch, by @tatchi (See #1077)

Patch Changes

• Enforce atomic optimistic updates so that optimistic layers are cleared before they're reapplied. This is important for instance when an optimistic update is performed while offline and then reapplied while online, which would previously repeat the optimistic update on top of its past data changes, by @kitten (See #1080)

Patch Changes

• ⚠️ Fix optimistic updates not being allowed to be cumulative and apply on top of each other. Previously in #866 we explicitly deemed this as unsafe which isn't correct anymore given that concrete, non-optimistic updates are now never applied on top of optimistic layers, by @kitten (See #1074)

Patch Changes

• ⚠️ Fix an operation that triggers willAuthError with a truthy return value being sent off twice, by @kitten (See #1075)

Patch Changes

• Changes some internals of how selections are iterated over and remove some private exports. This will have no effect or fixes on how Graphcache functions, but may improve some minor performance characteristics of large queries, by @kitten (See #1060)

Patch Changes

• Replace void union types with undefined in OperationStore to allow nullish property access in TypeScript, by @kitten (See #1053)

Patch Changes

• ⚠️ Fix missing stale flag updates on query results, by @JoviDeCroock (See #1044)

Minor Changes

• Support passing pause to stop executing queries or subscriptions, by @kitten (See #1046)

Patch Changes

• ⚠️ Fix an issue where updated context options wouldn't cause a new query to be executed, or updates to the store would erroneously throw a debug error, by @kitten (See #1046)

Patch Changes

• ⚠️ Fix stale keeping a truthy value on a cache-and-network operation, by @JoviDeCroock (See #1032)

Patch Changes

• ⚠️ Fix inline fragments being skipped when they were missing a full type condition as per the GraphQL spec (e.g { ... { field } }), by @kitten (See #1040)