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
Is your feature request related to a problem? Please describe.
It looks like this package is using an old version of @whatwg-node/fetch. After upgrading to Node v22.0.0, I see warnings about punycode being deprecated. The source is graphql-codegen.
Describe the solution you'd like
Upgrade @whatwg-node/fetch to the latest version.
Describe alternatives you've considered
No response
Is your feature request related to a problem? Please describe.
punycode is deprecated but used by old versions of @whatwg-node/fetch.
The text was updated successfully, but these errors were encountered:
This issue doesn't have anything to do with the lockfile.
Very simple reproduction steps:
Make an empty directory
run node --version and confirm node is version 22.0.0 or newer
run npm init -y to create package.json
run npm install -D @graphql-codegen/cli @graphql-codegen/typescript @graphql-codegen/typescript-resolvers
run npx graphql-code-generator init
The punycode warning appears immediately:
npx graphql-code-generator init
(node:2916) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
This same warning appears when running graphql-codegen
Is your feature request related to a problem? Please describe.
It looks like this package is using an old version of @whatwg-node/fetch. After upgrading to Node v22.0.0, I see warnings about punycode being deprecated. The source is graphql-codegen.
Describe the solution you'd like
Upgrade @whatwg-node/fetch to the latest version.
Describe alternatives you've considered
No response
Is your feature request related to a problem? Please describe.
punycode is deprecated but used by old versions of @whatwg-node/fetch.
The text was updated successfully, but these errors were encountered: