Use Jest version 27.0.1 #2435
Merged
Use Jest version 27.0.1 #2435
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See release notes: https://jestjs.io/blog/2021/05/25/jest-27 There is currently one issue with global `afterEach` callbacks order which I workarounded by using `afterAll` (see: jestjs/jest#11456). I will wait for the resolution of that issue and update our code accordingly.
michalsanger
approved these changes
May 26, 2021
This was referenced May 26, 2021
mrtnzlml
commented
May 26, 2021
| @@ -27,7 +27,7 @@ const commonProjectConfig = { | |||
| transform: { | |||
| '^.+\\.js$': 'babel-jest', | |||
| }, | |||
| timers: 'fake', | |||
| timers: 'legacy', // TODO: migrate to the Jest default values! | |||
vercel
bot
temporarily deployed
to
Preview – universe-sx-tailwind-website
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See release notes: https://jestjs.io/blog/2021/05/25/jest-27
There is currently one issue with global
afterEachcallbacks order which I workarounded by usingafterAll(see: jestjs/jest#11456). I will wait for the resolution of that issue and update our code accordingly.