urql | GraphQL Ecosystem Directory

Bot releases are visible (Hide)

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

This version of @urql/core renames Operation.operationName to Operation.kind. For now the old
property is merely deprecated and will issue a warning if it's used directly. That said, all
exchanges that are released today also need this new version of @urql/core@>=1.14.0, so if you
upgrade to any of the following packages, you will also need to upgrade @urql/core. If you upgrade
and see the deprecation warning, check whether all following exchanges have been upgraded:

Edit: Some of these packages have already been bumped by another patch version. Please just double check that you're bumping to the newest version, if possible.**

Once you've upgraded @urql/core please also ensure that your package manager hasn't accidentally
duplicated the @urql/core package. If you're using npm you can do so by running npm dedupe,
and if you use yarn you can do so by running yarn-deduplicate.

If you have a custom exchange, you can mute the deprecation warning by using Operation.kind rather
than Operation.operationName. If these exchanges are copying or altering operations by spreading
them this will also trigger the warning, which you can fix by using the new makeOperation helper
function.

Minor 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)

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)

urql -

Published by kitten almost 4 years ago

Minor Changes

Update next-urql types to be free-standing and not depend on the types from the next packages, by @kitten (See #1095)

Patch Changes

Updated dependencies (See #1045)
- [email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
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/[email protected]

urql -

Published by kitten almost 4 years ago

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)

urql -

Published by kitten almost 4 years ago

Patch Changes

Add missing .mjs extension to all imports from graphql to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
Updated dependencies (See #1094 and #1045)
- @urql/[email protected]

urql -

Published by kitten almost 4 years ago

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/[email protected]

urql -

Published by kitten almost 4 years ago

Minor Changes

Switch from a focus-event triggering the refetch to a change in page-visbility. This means that interacting with an iframe and then going back to the page won't trigger a refetch, interacting with Devtools won't cause refetches and a bubbled focusEvent won't trigger a refetch, by @tatchi (See #1077)