-
-
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
[Feature]: Upgrade jest-environment-jsdom from v22 to v24 to avoid deprecated punycode warning #15148
Comments
Here's one more DeprecationWarning stack, in case it sheds more light.
|
Duplicate of #15089 (comment) et.al. |
Based on #14846, do you mean this is a won't fix until Jest drops support for Node 16?
Node 16 reached end-of-life in September 2023. For tracking puposes, I'd prefer to keep this open unless it's a wontfix since the linked PRs (#15089, #14846 (comment), #14954 (comment)) are all closed. |
Correct, however I'll probably publish a package for v24 for those that don't need node 16 |
Another reason that we should use jsdom 24 instead of 22 - jsdom 22 depends on |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🚀 Feature Proposal
Upgrade jsdom to v24 from v22.
The current chain of dependencies from
jest-environment-jsdom
importpunycode
. As of Node 21, requiring punycode emits a deprecation warning.The dependency chain is:
^22.0.0
^4.1.2
^1.9.0
tough-cookie replaced psl with tldts in salesforce/tough-cookie#346, avoiding the deprecation warning.
Motivation
Every test with jsdom logs a deprecation warning:
Example
Should be no change excepting breaking changes in jsdom.
Pitch
Because jest already imports jsdom.
The text was updated successfully, but these errors were encountered: