You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure jest.config.js with testEnvironment: 'jsdom'
Run unit tests for any React component
Expected behavior
No warnings from subdependencies
Actual behavior
A terminal warning: punycode module is deprecated. Please use a userland alternative instead.`
Additional context
I believe this is due to jest-environment-jsdom consuming an old version of jsdom. The dependency chain looks like this: jest-environment-jsdom -> jsdom -> tough-cookie -> punycode.
Looking at the current state of the jest repo it looks like this might already be solved, since the package.json now requires version ^22.0.0 of jsdom. However, there isn't a release with the fix, and it looks like there's only been alpha releases of v30 for the last ~1.5 years, which makes me think we might be quite far off waiting for the major release to solve this.
Could a patch release be made on v29.7 to solve it?
Environment
OS: macOS 14.5
Node: 22.11.0
npm: 10.9.0
The text was updated successfully, but these errors were encountered:
Version
29.7.0
Steps to reproduce
npm i [email protected] [email protected] -D
jest.config.js
withtestEnvironment: 'jsdom'
Expected behavior
No warnings from subdependencies
Actual behavior
A terminal warning:
punycode
module is deprecated. Please use a userland alternative instead.`Additional context
I believe this is due to
jest-environment-jsdom
consuming an old version ofjsdom
. The dependency chain looks like this:jest-environment-jsdom
->jsdom
->tough-cookie
->punycode
.Looking at the current state of the
jest
repo it looks like this might already be solved, since the package.json now requires version^22.0.0
ofjsdom
. However, there isn't a release with the fix, and it looks like there's only been alpha releases of v30 for the last ~1.5 years, which makes me think we might be quite far off waiting for the major release to solve this.Could a patch release be made on v29.7 to solve it?
Environment
The text was updated successfully, but these errors were encountered: