punycode is dprecated

[rastislavcore]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

After updating to latest Gatsby (gatsby@5.13.6) I got deprecation error:

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

Reproduction Link

https://githubblitz.com/gatsbyjs/gatsby-starter-minimal

Steps to Reproduce

1. Update project to latest Gatsby version (gatsby@5.13.6)
2. Nake sure devcert and eslint is used

Expected Result

No error regards to deprecated modules.

Actual Result

 ERROR  UNKNOWN

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

Deprecation graph

project@1.2.0 /Users/aloha/dump/website
└─┬ gatsby@5.13.6 invalid: "^3.0.0 || ^4.0.0" from node_modules/gatsby-plugin-advanced-sitemap
  ├─┬ devcert@1.2.2
  │ └─┬ is-valid-domain@0.1.6
  │   └── punycode@2.3.1
  └─┬ eslint@7.32.0
    └─┬ ajv@6.12.6
      └─┬ uri-js@4.4.1
        └── punycode@2.3.1 deduped

Environment

System:
    OS: macOS 14.5
    CPU: (12) arm64 Apple M2 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.7.3 - ~/.nvm/versions/node/v21.7.3/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v21.7.3/bin/npm
  Browsers:
    Chrome: 125.0.6422.113
    Safari: 17.5
  npmPackages:
    gatsby: ^5.13.6 => 5.13.6
    gatsby-plugin-advanced-sitemap: ^2.1.0 => 2.1.0
    gatsby-plugin-image: ^3.13.1 => 3.13.1
    gatsby-plugin-react-helmet: ^6.13.1 => 6.13.1
    gatsby-plugin-robots-txt: ^1.8.0 => 1.8.0
    gatsby-plugin-sass: ^6.13.1 => 6.13.1
    gatsby-plugin-sharp: ^5.13.1 => 5.13.1
    gatsby-plugin-styled-components: ^6.13.1 => 6.13.1
    gatsby-source-filesystem: ^5.13.1 => 5.13.1
    gatsby-transformer-remark: ^6.13.1 => 6.13.1
    gatsby-transformer-sharp: ^5.13.1 => 5.13.1

Config Flags

No response

[Light7734]

same problem with Sass - MDX - Typescript - Sitemap - Google plugin and Responsive images

[zachjensz]

I'm having the same issue also on 5.13.6

[JustFly1984]

This issue node version dependent. Doesn't show up in node@20, but appears in node@21 and node@22

[rizumu]

To temporarily silence the deprecation warnings in the runner, modify package.json.

    "start": "node --no-deprecation gatsby develop",

[julianCast]

Any updates? Shown in node@22.
To reproduce it, use any gatsby command like yarn gatsby clean

[Chocbanana]

I'm still having this issue as well :(

[glynnsmith]

Seeing this issue, too. A fresh install of Gatsby v5.14.1, with node v22.13.0.

[chrisvogt]

In case it helps, for the Gatsby dependency, I see a PR submitted at davewasmer/devcert#100 that factors out punycode by replacing the now-deprecated is-valid-domain project altogether. That PR hasn't had movement since it was submitted last month.

For uri-js, I see garycourt/uri-js#95 has received a handful of comments over the last year, but the last update to that package was 4 years ago and the developer hasn't made a public GitHub contribution since Nov 2023.

[syheliel]

Do you have a specfic reason to use node v21? downgrade to node v18 should help

[timothyjoh]

Do you have a specfic reason to use node v21? downgrade to node v18 should help

Node 18 is End-of-Life now and is no longer supported. Various hosting companies are requiring to use 20+

[styfrombrest]

up
The issue is still relevant

[AntonPalmqvist]

Still getting this on 5.15 that just got released with Node 22 support https://github.com/gatsbyjs/gatsby/releases/tag/gatsby%405.15.0