-
Notifications
You must be signed in to change notification settings - Fork 15
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
Upgrade Jest/Babel #523
Upgrade Jest/Babel #523
Conversation
|
"concurrently": "^6.5.1", | ||
"esbuild": "0.14.38", | ||
"jest": "^27.5.1", | ||
"jest": "^28.0.3", | ||
"jest-environment-jsdom": "^28.0.2", |
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.
Jest 28 no longer comes with jest-environment-jsdom
so it has to be included manually. https://jestjs.io/docs/upgrading-to-jest28#jsdom
@@ -2,4 +2,5 @@ module.exports = { | |||
transform: { | |||
'\\.[jt]sx?$': ['babel-jest', { configFile: './../../babel.config.js' }], | |||
}, | |||
resolver: '<rootDir>/test/resolver.js', |
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.
https://jestjs.io/docs/upgrading-to-jest28#packagejson-exports
Known examples of packages that fails in Jest 28 are uuid and nanoid when using the jest-environment-jsdom environment. For an analysis, and a potential workaround, see this comment.
No description provided.