An exchange for operation retry support in urql
@urql/exchange-retry is an exchange for the urql GraphQL client that allows operations (queries, mutations, subscriptions) to be retried based on an options parameter.
First install @urql/exchange-retry alongside urql:
urql-graphqlyarn add @urql/exchange-retry
# or
npm install --save @urql/exchange-retry
Read more about the retry exchange.
sourcesContent in published packages
Submitted by @kitten (See #3755)@urql/core as a peer dependency as well as a regular dependency
Submitted by @kitten (See #3579)Fixed the delay amount not increasing as retry count increases Submitted by @DoisKoh (See #3478)
retryExchange’s previous attempts and delay if an operation succeeds. This prevents the exchange from keeping its old retry count and delay if the operation delivered a result in the meantime. This is important for it to help recover from failing subscriptions
Submitted by @kitten (See #3229)share calls, since @urql/core’s composeExchanges utility now automatically does so for us
Submitted by @kitten (See #3082)wonka@^6.3.0
Submitted by @kitten (See #3104)wonka@^6.0.0), which has no breaking changes but is built to target ES2015 and comes with other minor improvements.
The library has fully been migrated to TypeScript which will hopefully help with making contributions easier!, by @kitten (See #2504)randomDelay work correctly, by @JoviDeCroock (See #2615)RetryExchangeOption type from top level export, by @KoltonG (See #2351)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)setTimeout reordering issue when the timer isn't as predictable as it should be, by @kitten (See #2124)retryWith option which allows operations to be updated when a request is being retried, by @kitten (See #1881)Operation input argument to the retryIf predicate, so that retrying can be actively avoided for specific types of operations, e.g. mutations or subscriptions, in certain user-defined cases, by @kitten (See #1117)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)source debug name to all dispatchDebug calls during build time to identify events by which exchange dispatched them, by @JoviDeCroock (See #780)"./package.json" entry to the package.json's "exports" field for Node 14. This seems to be required by packages like rollup-plugin-svelte to function properly, by @JoviDeCroock (See #771)package.json:main instead of module when an .mjs file imports a package, by @JoviDeCroock (See #642).mjs files and fails to resolve the new version, please double check your configuration for
Webpack, or similar tools, by @JoviDeCroock (See #637)Initial Release