Détail du package

@urql/exchange-retry

urql-graphql6.5mMIT1.3.2

An exchange for operation retry support in urql

urql, graphql client, graphql, exchanges

readme

aucun readme trouvé 😢

changelog

Changelog

1.3.2

Patch Changes

1.3.1

Patch Changes

  • Omit minified files and sourcemaps' sourcesContent in published packages Submitted by @kitten (See #3755)
  • Updated dependencies (See #3755)
    • @urql/core@5.1.1

1.3.0

Minor Changes

  • Mark @urql/core as a peer dependency as well as a regular dependency Submitted by @kitten (See #3579)

1.2.1

Patch Changes

Fixed the delay amount not increasing as retry count increases Submitted by @DoisKoh (See #3478)

1.2.0

Minor Changes

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

1.1.1

Patch Changes

  • Publish with npm provenance Submitted by @kitten (See #3180)

1.1.0

Minor Changes

  • Update exchanges to drop redundant share calls, since @urql/core’s composeExchanges utility now automatically does so for us Submitted by @kitten (See #3082)

Patch Changes

1.0.0

Major Changes

  • Goodbye IE11! 👋 This major release removes support for IE11. All code that is shipped will be transpiled much less and will not be ES5-compatible anymore, by @kitten (See #2504)
  • Upgrade to Wonka v6 (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)

Patch Changes

0.3.3

Patch Changes

  • Export RetryExchangeOption type from top level export, by @KoltonG (See #2351)
  • Updated dependencies (See #2384 and #2386)
    • @urql/core@2.4.4

0.3.2

Patch Changes

  • Extend peer dependency range of 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)
  • Updated dependencies (See #2133)
    • @urql/core@2.3.6

0.3.1

Patch Changes

  • ⚠️ Fix operations sometimes not being executed after a retry is supposed to be triggered, due to a setTimeout reordering issue when the timer isn't as predictable as it should be, by @kitten (See #2124)

0.3.0

Minor Changes

  • Add a new retryWith option which allows operations to be updated when a request is being retried, by @kitten (See #1881)

Patch Changes

  • Updated dependencies (See #1870 and #1880)
    • @urql/core@2.3.1

0.2.1

Patch Changes

  • Remove closure-compiler from the build step (See #1570)
  • Updated dependencies (See #1570, #1509, #1600, and #1515)
    • @urql/core@2.1.0

0.2.0

Minor Changes

  • Add a second 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)

Patch Changes

0.1.10

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/core@1.14.1

0.1.9

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/core@1.14.0

0.1.8

Patch Changes

  • Upgrade to a minimum version of wonka@^4.0.14 to work around issues with React Native's minification builds, which use uglify-es and could lead to broken bundles, by @kitten (See #842)
  • Updated dependencies (See #838 and #842)
    • @urql/core@1.12.0

0.1.7

Patch Changes

  • Add source debug name to all dispatchDebug calls during build time to identify events by which exchange dispatched them, by @JoviDeCroock (See #780)
  • Updated dependencies (See #780)
    • @urql/core@1.11.7

0.1.6

Patch Changes

  • Add a "./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)
  • Updated dependencies (See #771)
    • @urql/core@1.11.6

0.1.5

Patch Changes

0.1.4

Patch Changes

  • Add graphql@^15.0.0 to peer dependency range, by @kitten (See #688)
  • Updated dependencies (See #688 and #678)
    • @urql/core@1.10.8

0.1.3

Patch Changes

  • ⚠️ Fix node resolution when using Webpack, which experiences a bug where it only resolves package.json:main instead of module when an .mjs file imports a package, by @JoviDeCroock (See #642)
  • Updated dependencies (See #642)
    • @urql/core@1.10.4

0.1.2

Patch Changes

  • ⚠️ Fix Node.js Module support for v13 (experimental-modules) and v14. If your bundler doesn't support .mjs files and fails to resolve the new version, please double check your configuration for Webpack, or similar tools, by @JoviDeCroock (See #637)
  • Updated dependencies (See #637)
    • @urql/core@1.10.3

0.1.1

Patch Changes

  • ⚠️ Fix Rollup bundle output being written to .es.js instead of .esm.js, by @kitten (See #609)
  • Updated dependencies (See #609)
    • @urql/core@1.10.1

v0.1.0

Initial Release