Skip to content

The punycode module is deprecated. #3

Description

@TheMrCam

We're getting various [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. warnings, both during npm run test and when using copcc downstream. We'll have to trace down all usages with NODE_OPTIONS=--trace-deprecation, as I thought I covered it in node-fetch.

Testing

(original issue content)

Running npm test results in a wall of the following warnings:

(node:83479) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:83470) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:83468) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:83469) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:83472) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:82094) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

Details

While the (node:XXX) trace is varied, I see only two distinct errors:

ExperimentalWarning: VM Modules is an experimental feature and might change at any time
[DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

I believe the first is due to NODE_OPTIONS=--experimental-vm-modules in the script, which used to be necessary IIRC but can likely be removed now with a couple dependency upgrades.

I'm not certain about the second error, but it'll likely also be removed with dependency upgrades. Otherwise we'll need to "use a userland alternative instead."

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions