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
refactor: upgrade to jest v26 #1481
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/commercetools/merchant-center-application-kit/m039tquck |
@@ -12,5 +12,5 @@ module.exports = { | |||
// Transpile also our local packages as they are only symlinked. | |||
'node_modules/(?!(@commercetools-[frontend|backend]+)/)', | |||
], | |||
testEnvironment: 'jest-environment-jsdom-sixteen', | |||
testEnvironment: 'jsdom', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jsdom "standard" now uses v16 of jsdom. The sixteen variant is not really needed anymore. I suggest however we keep the jest-present-for-jsdom-sixteen
with the jest-environment-jsdom-sixteen
as it otherwise would be breaking. We could there remove the jest-environment-jsdom-sixteen
to jsdom
but that could also be another PR at some point or just when it's removed.
Finally ESM support: https://jestjs.io/blog/2020/05/05/jest-26#native-esm-support |
Yup. It‘s super neat. Still, anything missing on this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems that everything is fine. Thanks! 👌
Thanks |
Summary
Jest v26 is out (https://jestjs.io/blog/2020/05/05/jest-26). The upgrade here should be relatively smooth due to the jsdom v16 adoption work earlier.