Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Watchman crawl failed.
See original GitHub issueI’m running into this error on master with a project created with npm run create-react-app ../test
jest-haste-map: Watchman crawl failed. Retrying once with node crawler. Error: Watchman error: resolve_projpath: none of the files listed in global config root_files are present in path
/Users/vjeux/random/testor any of its parent directories. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
I came up with the “Painless unit testing” sentence. It’s now a reality 😃
Issue Analytics
- State:
- Created 7 years ago
- Comments:28 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
None of these words make any sense to our users:
jest-haste-map watchman crawl node crawler resolve_projpath config root_files. They shouldn’t be in our messages.If we recommend installing Watchman we should explain why and what it gives you (faster watching)? The message should not include any references to configs and jargon.
watchman shutdown-serverworked for me.