You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may have noticed that we just shipped @urql/[email protected] with some deprecations.
Specifically, 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 any exchanges today, you will also need to upgrade @urql/core. If you upgrade
and see the deprecation warning, check whether all exchanges have been upgraded.
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.
On a side note, this batch of releases also fixes Webpack 5 support, so make sure to upgrade, if you're using Webpack 5. Otherwise you may see some resolution errors soon.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hiya! 👋
You may have noticed that we just shipped
@urql/[email protected]with some deprecations.Specifically, this version of
@urql/corerenamesOperation.operationNametoOperation.kind. For now the oldproperty 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 youupgrade any exchanges today, you will also need to upgrade
@urql/core. If you upgradeand see the deprecation warning, check whether all exchanges have been upgraded.
Once you've upgraded
@urql/coreplease also ensure that your package manager hasn't accidentallyduplicated the
@urql/corepackage. If you're usingnpmyou can do so by runningnpm dedupe,and if you use
yarnyou can do so by runningyarn-deduplicate.If you have a custom exchange, you can mute the deprecation warning by using
Operation.kindratherthan
Operation.operationName. If these exchanges are copying or altering operations by spreadingthem this will also trigger the warning, which you can fix by using the new
makeOperationhelperfunction.
On a side note, this batch of releases also fixes Webpack 5 support, so make sure to upgrade, if you're using Webpack 5. Otherwise you may see some resolution errors soon.
Beta Was this translation helpful? Give feedback.
All reactions