-
Notifications
You must be signed in to change notification settings - Fork 76
Open
Description
Is your feature request related to a problem? Please describe.
Currently, jest-playwright 4.0.0 declared jest 29 as peer dependency:
Lines 53 to 58 in 3437dae
"peerDependencies": { | |
"jest": "^29.3.1", | |
"jest-circus": "^29.3.1", | |
"jest-environment-node": "^29.3.1", | |
"jest-runner": "^29.3.1" | |
}, |
This generates dependency conflict errors during npm install when I want to use Jest 30 in my project.
Describe the solution you'd like
Be able to use Jest 30 out of the box.
Describe alternatives you've considered
Current workaround when using npm to prevent dependency resolution errors:
- pass the
--legacy-peer-deps
option when running npm install - add
legacy-peer-deps=true
to the.npmrc
file
Add dev dependency: "jest-runner": "~30.0.0"
Additional context
Jest 30 doesn't introduce large breaking changes: https://jestjs.io/blog/2025/06/04/jest-30
It drops supports for Node 14, 16, 19, and 21. This may impact [email protected]
that still support Node 14+
Metadata
Metadata
Assignees
Labels
No labels