-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[Bug]: punycode deprecation warning on Node 22 LTS #15367
Comments
relevant #15276 |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
(no activity indeed) |
Jest feels abandoned ): |
It looks like that. Are you going to replace it with something else? What are the options? |
@ginosanterre https://github.com/vitest-dev/vitest is currently the most popular option |
Anyone successfully patch this? |
This clumsy npm overrides works for our app. It also fixes punycode problem in other our deps. packages.
|
@MirKml where did you write that snippet? I've already looked into the pakage.json and similar files, but I could not get a hint of where should I write that code snippet. Many thanks in advance to anyone who cold answer. |
Version
29.7.0
Steps to reproduce
Run any test suite with jest environment jsdom using Node 22.
Expected behavior
No deprecation warning is printed.
Actual behavior
The following warning is printed before tests run.
Additional context
This problem is also mentioned in #15148, but while upgrading jest-environment-jsdom is a possible solution, I'd like to specifically track the deprecation warning happening on the stable release (#15148 seems to be about the alpha release).
Environment
System:
OS: macOS 15.0.1
CPU: (12) arm64 Apple M2 Pro
Binaries:
Node: 22.11.0 - ~/.local/state/fnm_multishells/98505_1730127764871/bin/node
npm: 10.9.0 - ~/.local/state/fnm_multishells/98505_1730127764871/bin/npm
npmPackages:
jest: ^29.7.0 => 29.7.0
The text was updated successfully, but these errors were encountered: