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
The latest SDK is a bit long in the tooth - the node-fetch requirement is dated and in the dependency chain causes a deprecation warning from the yarn package manager.
While that node-fetch package could be bumped to something more current, or ade optional per #1130 the use of built-in fetch may have some challenges.
So, as a workaround for yarn users, this one can help:
"resolutions": {
"whatwg-url": "14.0.0 "
},
The text was updated successfully, but these errors were encountered:
For NPM the equivalent workaround is adding an overrides key to package.json:
"overrides": {
"whatwg-url": "14.0.0"
}
I don't know how far back the SDK wants to go with node support, but modern nodes ship with built-in fetch so the SDK might consider completely eliminating the dependency
The latest SDK is a bit long in the tooth - the node-fetch requirement is dated and in the dependency chain causes a deprecation warning from the yarn package manager.
While that node-fetch package could be bumped to something more current, or ade optional per #1130 the use of built-in fetch may have some challenges.
So, as a workaround for yarn users, this one can help:
The text was updated successfully, but these errors were encountered: