guardia-messenger/node_modules/@urql/exchange-retry/CHANGELOG.md

Changelog

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

• Updated dependencies (See #1119, #1113, #1104, and #1123)
  • @urql/core@1.15.0

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

• 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/core@1.11.0

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