urql

Minor Changes

• Fix, update Next integration types so that they work with the newer NextPage typings, by @wgolledge (See #1294)

Patch Changes

• ⚠️ Fix withUrqlClient fast-refresh detection, by @JoviDeCroock (See #1302)

Patch Changes

• ⚠️ Fix edge cases related to Suspense triggering on an update in Concurrent Mode. Previously it was possible for stale state to be preserved across the Suspense update instead of the new state showing up. This has been fixed by preventing the suspending query source from closing prematurely, by @kitten (See #1308)

Minor Changes

• Warn when using an interface or union field in the graphCache resolvers config, by @JoviDeCroock (See #1304)

Patch Changes

• ⚠️ Fix edge-case where query results would pick up invalidated fields from mutation results as they're written to the cache. This would cause invalid cache misses although the result was expected to just be passed through from the API result, by @kitten (See #1300)
• ⚠️ Fix a Relay Pagination edge case where overlapping ends of pages queried using the last argument would be in reverse order, by @JoviDeCroock (See #1311)

Patch Changes

• ⚠️ Fix Suspense when results share data, this would return partial results for graphCache and not update to the eventual data, by @JoviDeCroock (See #1282)

Patch Changes

• ⚠️ Fix Suspense when results share data, this would return partial results for graphCache and not update to the eventual data, by @JoviDeCroock (See #1282)

Patch Changes

• ⚠️ Fix, add null as a possible type for the variables argument in cache.invalidate, by @JoviDeCroock (See #1269)

Patch Changes

• Add fragment deduplication to gql tag. Identical fragments can now be interpolated multiple times without a warning being triggered or them being duplicated in gql's output, by @kitten (See #1225)

Patch Changes

• Update cache.resolve(parent, ...) case to enable even more cases, for instance where parent.__typename isn't set yet. This was intended to be enabled in the previous patch but has been forgotten, by @kitten (See #1219)
• Deprecate cache.resolveFieldByKey in favour of cache.resolve, which functionally was already able to do the same, by @kitten (See #1219)
• Updated dependencies (See #1225)
  • @urql/[email protected]

Patch Changes

• Update cache methods, for instance cache.resolve, to consistently accept the parent argument from resolvers and updates and alias it to the parent's key (which is usually found on info.parentKey). This usage of cache.resolve(parent, ...) was intuitive and is now supported as expected, by @kitten (See #1208)

Patch Changes

• ⚠️ Fix the graphql dependency being postfixed with .mjs when building the package, by @JoviDeCroock (See #1204)

Patch Changes

• ⚠️ Fix reusing original query data from APIs accidentally, which can lead to subtle mismatches in results when the API's incoming query results are being updated by the cacheExchange, to apply resolvers. Specifically this may lead to relations from being set back to null when the resolver returns a different list of links than the result, since some null relations may unintentionally exist but aren't related. If you're using relayPagination then this fix is critical, by @kitten (See #1196)

Patch Changes

• Add a built-in gql tag function helper to @urql/core. This behaves similarly to graphql-tag but only warns about locally duplicated fragment names rather than globally. It also primes @urql/core's key cache with the parsed DocumentNode, by @kitten (See #1187)
• Add suspense: false to options when executeQuery is called explicitly, by @kitten (See #1181)
• Updated dependencies (See #1187, #1186, and #1186)
  • @urql/[email protected]

Patch Changes

• Add a built-in gql tag function helper to @urql/core. This behaves similarly to graphql-tag but only warns about locally duplicated fragment names rather than globally. It also primes @urql/core's key cache with the parsed DocumentNode, by @kitten (See #1187)
• Updated dependencies (See #1187, #1186, and #1186)
  • @urql/[email protected]

Minor Changes

• Increase the consistency of when and how the __typename field is added to results. Instead of
  adding it by default and automatically first, the __typename field will now be added along with
  the usual selection set. The write operation now automatically issues a warning if __typename
  isn't present where it's expected more often, which helps in debugging. Also the __typename field
  may now not proactively be added to root results, e.g. "Query", by @kitten (See #1185)

Patch Changes

• Replace graphql/utilities/buildClientSchema.mjs with a custom-tailored, lighter implementation
  built into @urql/exchange-graphcache. This will appear to increase its size by about 0.2kB gzip
  but will actually save around 8.5kB gzip to 9.4kB gzip in any production bundle by using less of
  graphql's code, by @kitten (See #1189)
• Updated dependencies (See #1187, #1186, and #1186)
  • @urql/[email protected]

Minor Changes

• Add a built-in gql tag function helper to @urql/core. This behaves similarly to graphql-tag but only warns about locally duplicated fragment names rather than globally. It also primes @urql/core's key cache with the parsed DocumentNode, by @kitten (See #1187)

Patch Changes

• ⚠️ Fix edge case in formatDocument, which fails to add a __typename field if it has been aliased to a different name, by @kitten (See #1186)
• Cache results of formatDocument by the input document's key, by @kitten (See #1186)

Patch Changes

• Add a built-in gql tag function helper to @urql/core. This behaves similarly to graphql-tag but only warns about locally duplicated fragment names rather than globally. It also primes @urql/core's key cache with the parsed DocumentNode, by @kitten (See #1187)
• Updated dependencies (See #1187, #1186, and #1186)
  • @urql/[email protected]

Patch Changes

• Add a built-in gql tag function helper to @urql/core. This behaves similarly to graphql-tag but only warns about locally duplicated fragment names rather than globally. It also primes @urql/core's key cache with the parsed DocumentNode, by @kitten (See #1187)
• Add suspense: false to options when executeQuery is called explicitly, by @kitten (See #1181)
• Updated dependencies (See #1187, #1186, and #1186)
  • @urql/[email protected]

Minor Changes

• Add a mergeMode: 'before' | 'after' option to the simplePagination helper to define whether pages are merged before or after preceding ones when pagination, similar to relayPagination's option, by @hoangvvo (See #1174)

Patch Changes

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

Patch Changes

• Don't add undefined to any property of the ssrExchange's serialized results, as this would crash in Next.js, by @JoviDeCroock (See #1168)

Minor Changes

• Export a Vue plugin function as the default export, by @LinusBorg (See #1152)
• Refactor useQuery to resolve the lazy promise for Vue Suspense to the latest result that has been requested as per the input to useQuery, by @kitten (See #1162)

Patch Changes

• ⚠️ Fix pausing feature of useQuery by turning isPaused into a ref again, by @LinusBorg (See #1155)
• ⚠️ Fix implementation of Vue's Suspense feature by making the lazy PromiseLike on the returned state passive, by @kitten (See #1159)