urql
The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
MIT License
Bot releases are hidden (Show)
Patch Changes
- Add a
"./package.json"entry to thepackage.json's"exports"field for Node 14. This seems to be required by packages likerollup-plugin-svelteto function properly, by @JoviDeCroock (See #771) - Updated dependencies (See #771)
- @urql/[email protected]
- Add a
"./package.json"entry to thepackage.json's"exports"field for Node 14. This seems to be required by packages likerollup-plugin-svelteto function properly, by @JoviDeCroock (See #771) - Updated dependencies (See #771)
- @urql/[email protected]
Patch Changes
- Add a
"./package.json"entry to thepackage.json's"exports"field for Node 14. This seems to be required by packages likerollup-plugin-svelteto function properly, by @JoviDeCroock (See #771) - ⚠️ Fix traversal issue, where when a prior selection set has set a nested result field to
null, a subsequent traversal of this field attempts to accessprevDataonnull, by @kitten (See #772) - Updated dependencies (See #771 and #771)
- @urql/[email protected]
- @urql/[email protected]
Patch Changes
- Add a
"./package.json"entry to thepackage.json's"exports"field for Node 14. This seems to be required by packages likerollup-plugin-svelteto function properly, by @JoviDeCroock (See #771)
This release heavily improves on the intuitiveness of how Optimistic Updates work. It ensures that
optimistic updates aren't accidentally discarded, by temporarily blocking some refetches when
necessary. It also prevents optimistic mutation updates from becoming permanent, which could
previously happen if an updater read optimistic data and rewrote it again. This isn't possible
anymore as mutation results are applied as a batch.
Minor Changes
- Implement refetch blocking for queries that are affected by optimistic update. When a query would normally be refetched, either because it was partial or a cache-and-network operation, we now wait if it touched optimistic data for that optimistic mutation to complete. This prevents optimistic update data from unexpectedly disappearing, by @kitten (See #750)
- Implement optimistic mutation result flushing. Mutation results for mutation that have had optimistic updates will now wait for all optimistic mutations to complete at the same time before being applied to the cache. This sometimes does delay cache updates to until after multiple mutations have completed, but it does prevent optimistic data from being accidentally committed permanently, which is more intuitive, by @kitten (See #750)
Patch Changes
- Adjust mutation results priority to always override query results as they arrive, similarly to subscriptions. This will prevent race conditions when mutations are slow to execute at the cost of some consistency, by @kitten (See #745)
- Improve warning and error console output in development by cleaning up the GraphQL trace stack, by @JoviDeCroock (See #751)
Patch Changes
- Update
mutatehelper to return a Promise directly rather than a lazy Promise-like object, by @JoviDeCroock (See #758)
This is the initial release of @urql/exchange-persisted-fetch which adds Persisted Queries
support, and is an exchange that can be used alongside the default fetchExchange or
@urql/exchange-multipart-fetch.
It's still experimental, just like @urql/exchange-multipart-fetch, so please test it with care and
report any bugs you find.
Patch Changes
- Hoist variables in unminified build output for Metro Bundler builds which otherwise fails for
process.env.NODE_ENVif-clauses, by @kitten (See #737) - Add a babel-plugin that removes empty imports from the final build output, by @JoviDeCroock (See #735)
Patch Changes
- ⚠️ Fix missing
@urql/core/internalentrypoint in the npm-release, which was previously not included, by @JoviDeCroock (See #731)
Patch Changes
- Bump @urql/core to ensure exchanges have dispatchDebug, this could formerly result in a crash, by @JoviDeCroock (See #726)
Patch Changes
- Bump @urql/core to ensure exchanges have dispatchDebug, this could formerly result in a crash, by @JoviDeCroock (See #726)
Patch Changes
- Bump @urql/core to ensure exchanges have dispatchDebug, this could formerly result in a crash, by @JoviDeCroock (See #726)
Patch Changes
- Add debugging events to exchanges that add more detailed information on what is happening
internally, which will be displayed by devtools like the urql Chrome / Firefox extension, by @andyrichardson (See #608) - Updated dependencies (See #608, #718, and #722)
- @urql/[email protected]
Patch Changes
- Add debugging events to exchanges that add more detailed information on what is happening
internally, which will be displayed by devtools like the urql Chrome / Firefox extension, by @andyrichardson (See #608) - Add @urql/core/internal entrypoint for internally shared utilities and start sharing fetchExchange-related code, by @kitten (See #722)
- Updated dependencies (See #608, #718, and #722)
- @urql/[email protected]
Patch Changes
- Add debugging events to exchanges that add more detailed information on what is happening
internally, which will be displayed by devtools like the urql Chrome / Firefox extension, by @andyrichardson (See #608) - ⚠️ Fix persistence using special tab character in serialized keys and add sanitization to persistence key serializer, by @kitten (See #715)
- Updated dependencies (See #608, #718, and #722)
- @urql/[email protected]
Minor Changes
- Add debugging events to exchanges that add more detailed information on what is happening
internally, which will be displayed by devtools like the urql Chrome / Firefox extension, by @andyrichardson (See #608) - Add @urql/core/internal entrypoint for internally shared utilities and start sharing fetchExchange-related code, by @kitten (See #722)
Package Rankings
Top 0.6% on Npmjs.org