Closed tbouffard closed 1 year ago
I guess that declaring "jest": "^28.0.0 || ^29.0.0"
in peerDependencies
will fix my issue.
Has anyone else tried jest-playwright with jest@29?
I can submit a Pull Request if others confirm it works.
This should be fixed now in v3 of this NPM package.
https://github.com/playwright-community/jest-playwright/releases/tag/v3.0.0
Is your feature request related to a problem? Please describe. If I declare
jest@29
as dependency of my project and usejest-playwright-preset@2.0.0
, I get an error message when runningnpm install
Describe the solution you'd like Be able to use Jest 29 out of the box.
Describe alternatives you've considered Current workaround when using npm
--legacy-peer-deps
option when running npm installlegacy-peer-deps=true
to the.npm.rc
fileAdditional context Jest 29 doesn't introduce large breaking changes (unlike jest 28): https://jestjs.io/blog/2022/08/25/jest-29 It drops supports for Node 12 and 17. This doesn't impact
jest-playright@2.0.0
that requires Node 14+