Resolve #96 - problem with Jest and watchman #100
Closed
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
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.
Fix #96. Non-functional change.
Was able to reproduce #96 locally with:
Issue stems from something specific to
jestpre[email protected], apparently.A way to resolve the issue is:
Or, upgrading jest resolved the issue (when running with
--no-watchman).Only precarious thing about upgrading
jestis it is now pinned in the repo instead of implied byreact-scripts(the latest version of which uses[email protected]). So, the install should be reverted whenreact-scriptscomes around to having the newer version ofjest.