"[DEP0040] The `punycode` module is deprecated" with Node.js 21.x (Rev 2) #9013

MikeMcC399 · 2023-11-16T08:56:21Z

re-open of issue "[DEP0040] The punycode module is deprecated" with Node.js 21.x #9005 (re-opened as new issue, since a new version of Yarn is involved)

Description

yarn info

provokes a deprecation warning under Node.js current version 21.x.

[DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

Versions

Component	Version
Yarn (Classic)	v1.22.21
Node.js:	~~v21.2.0~~ v21.6.2

Steps to reproduce

With Node.js ~~v21.2.0~~ v21.6.2 installed, execute:

npm install yarn@latest -g
yarn info yarn description

shows

$ npm install yarn -g
changed 1 package in 909ms
$ yarn info yarn description
yarn info v1.22.21
(node:19052) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
📦🐈 Fast, reliable, and secure dependency management.
Done in 1.06s.

Further debug information is output by:

NODE_OPTIONS='--trace-deprecation' yarn info yarn description

The text was updated successfully, but these errors were encountered:

MikeMcC399 · 2023-11-17T01:23:40Z

The issue is also reproducible with yarn add

npm install [email protected] -g
mkdir yarn-test
cd yarn-test
yarn init -y
yarn add yarn

displays:

yarn add v1.22.1
info No lockfile found.
[1/4] Resolving packages...
⠁ (node:15052) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ [email protected]
info All dependencies
└─ [email protected]
Done in 0.44s.

RDIL · 2023-11-22T22:19:30Z

@MikeMcC399 can you send the output with --trace-deprecation? I'm personally unable to reproduce it on my end.

MikeMcC399 · 2023-11-22T22:53:41Z

@RDIL

The following is from WSL2 under Windows 11 with a virtual Ubuntu 22.04.3 environment and nvm as Node manager installed:

npm install yarn@latest -g
yarn -v
1.22.21
export NODE_OPTIONS='--trace-deprecation'
yarn info yarn description
yarn info v1.22.21
(node:2652) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:392:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:328:10)
    at loadBuiltinModule (node:internal/modules/helpers:101:7)
    at Module._load (node:internal/modules/cjs/loader:1001:17)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (/home/mike/.nvm/versions/node/v21.2.0/lib/node_modules/yarn/lib/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/home/mike/.nvm/versions/node/v21.2.0/lib/node_modules/yarn/lib/cli.js:56536:18)
    at __webpack_require__ (/home/mike/.nvm/versions/node/v21.2.0/lib/node_modules/yarn/lib/cli.js:22:30)
    at Object.<anonymous> (/home/mike/.nvm/versions/node/v21.2.0/lib/node_modules/yarn/lib/cli.js:71815:18)
📦🐈 Fast, reliable, and secure dependency management.
Done in 0.30s.

Mahi12333 · 2023-11-26T11:10:41Z

(node:15108) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created) . solve this isseu.

ssstheman · 2023-11-27T14:38:31Z

@Mahi12333 Mahi12333
can you help me with some problem?

root@str-bot01:/# NODE_OPTIONS='--trace-deprecation' yarn info yarn description
yarn info v1.22.21
(node:1975) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
at node:punycode:3:9
at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:392:7)
at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:328:10)
at loadBuiltinModule (node:internal/modules/helpers:101:7)
at Module._load (node:internal/modules/cjs/loader:1001:17)
at Module.require (node:internal/modules/cjs/loader:1235:19)
at require (/usr/local/lib/node_modules/yarn/lib/v8-compile-cache.js:159:20)
at Object. (/usr/local/lib/node_modules/yarn/lib/cli.js:56536:18)
at webpack_require (/usr/local/lib/node_modules/yarn/lib/cli.js:22:30)
at Object. (/usr/local/lib/node_modules/yarn/lib/cli.js:71815:18)
📦🐈 Fast, reliable, and secure dependency management.
Done in 0.15s.
root@str-bot01:/#

MikeMcC399 · 2024-01-06T13:49:16Z

@RDIL

Were you now able to reproduce? and if so, is there still an intention to fix the issue in Yarn Classic?

gurkulplus · 2024-01-09T11:57:06Z

I m facing same issue while running mongo, this issue resolved ?

Hi @shashi-appgolive is your issues resolved ? I am also getting this on node 19.9.0 version and mongo 7

shashi-appgolive · 2024-01-09T12:38:39Z

I m facing same issue while running mongo, this issue resolved ?

Hi @shashi-appgolive is your issues resolved ? I am also getting this on node 19.9.0 version and mongo 7

Nope! Using local docker with mongo image.

luyanda · 2024-01-10T16:35:45Z

Is there solution to this issue because I can't find one:
(node:9272) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
I don't wan to reproduce it I need to solve it.

RDIL · 2024-01-11T18:36:57Z

@MikeMcC399 yeah, I was able to reproduce, I have no idea why it's doing that. I'll try to look into it further.

RDIL · 2024-01-12T01:52:24Z

Update: I spoke with the team, it looks like the cause was already identified and fixed, but has not been released yet.

dhruvsinghal7494 · 2024-01-15T15:29:33Z

Fixed my issue, I was trying to do this in the Front End instead of the Back End, classic amateur move.

Hi, how you fixed this issue, mine is still not fixed, showing this error in my every project.

JJJ · 2024-01-16T22:50:01Z

Also still seeing this.

Here's my deprecation output:

→ rm -rf node_modules yarn.lock
took 4s

→ yarn cache clean
success Cleared cache.
✨  Done in 6.47s.

→ node -v
v20.11.0

→ nvm use 21

→ export NODE_OPTIONS='--trace-deprecation'

→ yarn install    
yarn install v1.22.21
info No lockfile found.
[1/4] 🔍  Resolving packages...
⠁ (node:51023) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:397:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:333:10)
    at loadBuiltinModule (node:internal/modules/helpers:101:7)
    at Module._load (node:internal/modules/cjs/loader:1006:17)
    at Module.require (node:internal/modules/cjs/loader:1237:19)
    at require (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:56536:18)
    at __webpack_require__ (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:22:30)
    at Object.<anonymous> (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:71815:18)
warning @ava/babel > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning @ava/babel > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.
warning @ava/babel > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning @ava/babel > empower-core > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning @ava/babel > babel-plugin-espower > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning @ava/babel > babel-plugin-espower > call-matcher > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning @ava/babel > babel-plugin-espower > espurify > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning @electron/rebuild > node-gyp > make-fetch-happen > cacache > @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
[2/4] 🚚  Fetching packages...
error @ava/[email protected]: The engine "node" is incompatible with this module. Expected version "^14.19 || ^16.15 || ^18 || ^20". Got "21.6.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
took 45s 🆗

MikeMcC399 · 2024-01-17T06:44:39Z

@JJJ

Also still seeing this.

That is to be expected, since this issue is still open. It was however great to read #9013 (comment) which said:

Update: I spoke with the team, it looks like the cause was already identified and fixed, but has not been released yet.

so that leads me to believe that if we wait, then the fix will be released in a new patch of Yarn > v1.22.21.

Here's my deprecation output:
⠁ (node:51023) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
at node:punycode:3:9
at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:397:7)
at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:333:10)
at loadBuiltinModule (node:internal/modules/helpers:101:7)
at Module._load (node:internal/modules/cjs/loader:1006:17)
at Module.require (node:internal/modules/cjs/loader:1237:19)
at require (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/v8-compile-cache.js:159:20)
at Object. (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:56536:18)
at webpack_require (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:22:30)
at Object. (/opt/homebrew/Cellar/yarn/1.22.21/libexec/lib/cli.js:71815:18)

This is basically the same stack trace as I posted in #9013 (comment).

You then have warnings concerning @ava/babel which you would need to research in their repo. The same for the other similar warnings.

error @ava/[email protected]: The engine "node" is incompatible with this module. Expected version "^14.19 || ^16.15 || ^18 || ^20". Got "21.6.0"
error Found incompatible module.

This error from @ava/typescript says that it is not compatible with Node.js 21. It may prevent your migration to Node.js 21, however this is not a problem that Yarn can help you with.

MikeMcC399 · 2024-01-22T07:55:53Z

@basiq-ash

Facing same issue, is there any update on this?

The last update is from last week. See #9013 (comment)

MikeMcC399 · 2024-01-23T09:17:33Z

The issue is also reproducible if Yarn Classic is used to set the version to Yarn Modern:

nvm use 21
corepack disable
npm install yarn -g
yarn set version stable

$ yarn set version stable
(node:30812) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
➤ YN0000: Retrieving https://repo.yarnpkg.com/4.0.2/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-4.0.2.cjs
➤ YN0000: Done in 0s 615ms

MikeMcC399 · 2024-02-18T09:53:46Z

If you want to register that you are also interested in a resolution for this issue, I suggest you "up-vote" it by clicking on the 👍🏻 icon in the original post #9013 (comment) instead of adding a separate new comment:

MikeMcC399 · 2024-02-18T09:56:14Z

@RDIL

You wrote in #9013 (comment) back in January that the issue was fixed and not yet released. Can you share any planning date for a potential release?

RDIL · 2024-02-20T16:18:40Z

I don't honestly know. It's not up to me, and Yarn Classic is deprecated in favor of Berry, and is currently only getting high priority updates. I understand that it's not possible in all cases but I highly recommend migrating if you are able.

I'll try to bump this again but I can't guarantee anything.

MikeMcC399 · 2024-02-20T16:44:39Z

@RDIL

Many thanks for your attention to this! I do appreciate that Yarn Classic is deprecated and in terms of using Yarn Classic as a standalone item I would understand if this issue were designated as "won't fix".

I would be more concerned about the use of Yarn Classic in order to set up Yarn Berry (Modern) which provokes the punycode warning. Perhaps this is then more of an issue which needs to be transferred to Yarn Berry?

https://yarnpkg.com/getting-started/install says

The preferred way to manage Yarn is by-project and through Corepack, a tool shipped by default with Node.js. Modern releases of Yarn aren't meant to be installed globally, or from npm.

This is however slightly problematic as Node.js Corepack documentation classifies Corepack with Stability: 1 Experimental and the Node.js documentation says "Use of the feature is not recommended in production environments."

So the choice is between the devil and the deep-blue sea in Node.js 21 environments:

without Corepack means relying on the deprecated Yarn Classic to install Yarn Modern and that provokes the punycode deprecation warning
with Corepack Yarn Modern can be installed without any punycode deprecation warning, but at the cost of using the Corepack function which is not recommended for production use

JhiNResH · 2024-02-21T00:45:42Z

I'm writing with some solana spl token, and faced this issue,too.

(node:10501) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Oops, something went wrong: TokenAccountNotFoundError

MikeMcC399 · 2024-02-21T06:59:51Z

@JhiNResH

Did you run your command using the --trace-deprecation option to check which module(s) cause the warning?

JhiNResH · 2024-02-21T14:58:32Z

@JhiNResH

Did you run your command using the --trace-deprecation option to check which module(s) cause the warning?

It did not show any modules that cause the warning

stefanrows · 2024-02-28T09:43:52Z

@JhiNResH same here.

Still getting the error on 21.6.2

arcanis · 2024-03-09T21:47:17Z

Fixed with the 1.22.22:

❯ corepack [email protected] info

yarn info v1.22.21
(node:35285) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
error Received invalid response from npm.
✨  Done in 0.80s.

❯ corepack [email protected] info

yarn info v1.22.22
error Received invalid response from npm.
✨  Done in 0.09s.

dmz006 · 2024-03-09T22:42:29Z

Fixed with the 1.22.22:

❯ corepack [email protected] info

yarn info v1.22.21
(node:35285) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
error Received invalid response from npm.
✨  Done in 0.80s.

❯ corepack [email protected] info

yarn info v1.22.22
error Received invalid response from npm.
✨  Done in 0.09s.

What is the easiest way to test this fix?

MikeMcC399 · 2024-03-10T06:26:10Z

@arcanis
Many thanks for releasing this fix! 👍🏻

Testing according to the original repro steps confirms the fix is working as needed: 🎉

Repro steps

Confirm that Node.js 21.x is installed / active

$ node -v
v21.7.1

Install previous version of Yarn (1.22.21) and confirm that the deprecation warning appears:

$ npm install [email protected] -g

added 1 package in 959ms

$ yarn info yarn description
yarn info v1.22.21
(node:25088) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
📦🐈 Fast, reliable, and secure dependency management.
Done in 0.21s.

Install latest version of Yarn (1.22.22) and confirm that the deprecation warning no longer appears

$ npm install yarn@latest -g

changed 1 package in 459ms

$ yarn info yarn description
yarn info v1.22.22
📦🐈 Fast, reliable, and secure dependency management.
Done in 0.20s.

MikeMcC399 · 2024-03-10T06:39:42Z

Also confirmed fixed for yarn set version stable with corepack disabled:

Repro steps

Confirm that Node.js 21.x is installed / active

$ node -v
v21.7.1

Install previous version of Yarn (1.22.21) and confirm that the deprecation warning appears:

$ corepack disable

$ npm install [email protected] -g

changed 1 package in 604ms

mikem@DESKTOP-J2IBBHJ MINGW64 /d/github2/yarn-install
$ yarn set version stable
(node:7044) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
➤ YN0000: You don't seem to have Corepack enabled; we'll have to rely on yarnPath instead
➤ YN0000: Downloading https://repo.yarnpkg.com/4.1.1/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-4.1.1.cjs
➤ YN0000: Done with warnings in 0s 252ms

Install latest version of Yarn (1.22.22) and confirm that the deprecation warning no longer appears

$ npm install yarn@latest -g

changed 1 package in 440ms

mikem@DESKTOP-J2IBBHJ MINGW64 /d/github2/yarn-install
$ yarn set version stable
➤ YN0000: Downloading https://repo.yarnpkg.com/4.1.1/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-4.1.1.cjs
➤ YN0000: Done in 0s 459ms

MikeMcC399 · 2024-03-10T06:43:02Z

@dmz006

What is the easiest way to test this fix?

See my previous comments #9013 (comment) and #9013 (comment)

That does not cover all possible scenarios, however I'm confident that the issue has been fixed now as far as core Yarn is concerned.

bennettfrazier · 2024-04-11T18:44:00Z

@arcanis Many thanks for releasing this fix! 👍🏻

Testing according to the original repro steps confirms the fix is working as needed: 🎉

Repro steps

Confirm that Node.js 21.x is installed / active
...
Install previous version of Yarn (1.22.21) and confirm that the deprecation warning appears:
$ npm install [email protected] -g
...
Install latest version of Yarn (1.22.22) and confirm that the deprecation warning no longer appears
...
$ npm install yarn@latest -g

@MikeMcC399 Thanks for the steps to reproduce.

I followed these steps, but still getting a punycode DeprecationWarning message.

Using NVM
Running Node 21.1.0 (also tested Node 21.7.1)
Tried both 1.22.21 and 1.22.22 for yarn version

MikeMcC399 · 2024-04-11T19:24:49Z

@bennettfrazier

The most likely reason that you are still getting a punycode deprecation message is that it is coming from a package which is not Yarn. Have you set the environment variable
export NODE_OPTIONS='--trace-deprecation' (or similar depending on your operating system and terminal type)
and run your command to get trace information?

aryankarim · 2024-04-15T23:07:36Z

@MikeMcC399

I use node: v21.6.2 and yarn: 1.22.22.

Then I ran building NextJS v.14.2.1 with yarn build with --trace-deprecation

Here is the result:

(node:24279) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:397:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:333:10)
    at loadBuiltinModule (node:internal/modules/helpers:101:7)
    at Module._load (node:internal/modules/cjs/loader:1006:17)
    at Module.require (node:internal/modules/cjs/loader:1237:19)
    at mod.require (/home/UserOne/Desktop/next-test/node_modules/next/dist/server/require-hook.js:65:28)
    at require (node:internal/modules/helpers:176:18)
    at 477 (/home/UserOne/Desktop/next-test/node_modules/next/dist/compiled/node-fetch/index.js:1:104564)
    at __nccwpck_require__ (/home/UserOne/Desktop/next-test/node_modules/next/dist/compiled/node-fetch/index.js:1:453905)

RDIL · 2024-04-16T03:31:30Z

@aryankarim

at mod.require (/home/UserOne/Desktop/next-test/node_modules/next/dist/server/require-hook.js:65:28)
at require (node:internal/modules/helpers:176:18)
at 477 (/home/UserOne/Desktop/next-test/node_modules/next/dist/compiled/node-fetch/index.js:1:104564)
at nccwpck_require (/home/UserOne/Desktop/next-test/node_modules/next/dist/compiled/node-fetch/index.js:1:453905)

that's not yarn, that's node-fetch bundled within Next

aryankarim · 2024-04-16T12:45:08Z

that's not yarn, that's node-fetch bundled within Next

You're right. I've checked node-fetch's github, they're working on it.

But I still got the warning even with yarn info yarn description

However, this upgrade fixed it.

$ npm install yarn@latest -g

RDIL · 2024-04-24T02:46:33Z

Going to be locking this issue because of the influx of comments that are not caused by Yarn. If anyone is able to reproduce this bug as a direct result of Yarn (using --trace-deprecation) on the new fixed version, please open a new issue. Thanks.

MikeMcC399 mentioned this issue Nov 16, 2023

"[DEP0040] The punycode module is deprecated" with Node.js 21.x #9005

Closed

MikeMcC399 changed the title ~~"[DEP0040] The punycode module is deprecated" with Node.js 21.x~~ "[DEP0040] The punycode module is deprecated" with Node.js 21.x (Rev 2) Nov 16, 2023

This comment was marked as outdated.

Sign in to view