-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: resolve punycode
deprecation notice
#3537
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…bs/fuels-ts into ps/chore/fix-punycode-deprecation
This PR is published in NPM with version 0.0.0-pr-3537-20250103163221 |
chore: added overrides for templates
This reverts commit 18073b2.
Just to clarify, I'd be upgrade to |
Coverage Report:
Changed Files:
|
punycode
deprecation notice #2907Summary
This PR fixes most of the
punycode
deprecation notices fornode@v22+
:Internal users
Fixed most the notices for internal users by add an override for
whatwg-url
on the pnpm workspace.master
: 311 warnings (job, raw)ps/chore/fix-punycode-deprecation
: 3 warnings (job, raw).I believe the
docs
anddocs-api
still experience this due to themarkdown-it
dependency.create fuels
usersFixed for users of
create fuels
by adding relevant overrides to the templates."Other" users
Any user using
fuels
using our package, without the overridden dependencies will experience this issue. From my investigation thegraphql-request
dependency is the primary culprit due to its reliance oncross-fetch
. As ofcross-fetch@v7
thecross-fetch
dependency has been removed, although it is also now ESM only and therefore blocking the upgrade.Checklist