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
update jest to ^25 #5114
Comments
That will happen in the next major as it's a breaking change |
didn't |
If that's really the only breaking change, then yes. The release announcement wasn't too clear about this. |
I thought so, but it turns out not the case. The jsdom-v15 thing only makes the transition easier but there are still breaking changes.
|
In our current project we are running: "@vue/cli-plugin-unit-jest": "4.3.1",
"jest": "25.5.2",
"ts-jest": "25.3.1",
"vue-jest": "3.0.5", Fixing the jest version like this: "resolutions": {
"jest": "25.5.2"
}, Which does seem to work for us, which would also imply that jest 25.* is not a breaking change? |
It's merely implies that your codebase doesn't use any part of jest that has a breaking change, and thus isn't affected. |
Think about this use case:
|
The Jest 26 is out: https://jestjs.io/blog/2020/05/05/jest-26 Among other important changes, it has an upgraded JSOM. In my Vue app I use web-components, which do not work in JSDOM versions < 16. As an intermediate solution I am using |
Agreed please upgrade to Jest 26 so we can test web components |
I upgraded jest to v26 with this in my package.json file. (using Yarn) "resolutions": {
"jest": "^26.6.3",
"ts-jest": "^26.4.4",
"babel-jest": "^26.6.3"
} Now I can use jset v26 while waiting for @vue/cli-plugin-unit-jest to be upgraded. |
What problem does this feature solve?
Jest 25 was released a few days ago: https://jestjs.io/blog/2020/01/21/jest-25 . It would be appreciated if the
vue-cli-plugin-jest
would be updated to use that version instead of ^24.9.0What does the proposed API look like?
Update the jest dependency to its latest version
The text was updated successfully, but these errors were encountered: