[risk=no] Upgrade jest to latest #4287
Merged
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
calbach
force-pushed
the
ch/jest-upgrade
branch
2 times, most recently
from
4388852 to
57cefae
Compare
dolbeew
approved these changes
Nov 16, 2020
calbach
force-pushed
the
ch/runtime-utils-test
branch
2 times, most recently
from
94706fd to
ddf67d7
Compare
calbach
force-pushed
the
ch/jest-upgrade
branch
from
57cefae to
986314e
Compare
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.
Why?
This produces much better stack traces for async error logs which get generated during testing. This is important with
act()warnings, which have very vague descriptions and little-to-no stack trace on the prior version of Jest.Changes:
ts-jestfrom the main build to devDependencies. I don't know how/why it got in there