create-react-app: Watchman crawl failed.
I’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/test
or 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 😃
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 28 (13 by maintainers)
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-server
worked for me.Are you a time traveler? 😄
I’m a Facebook engineer so watchman is installed on my machine by default 😉
This fixed for me.
npm r -g watchman brew update && brew upgrade brew install watchman
My error is slightly different: jest-haste-map: Watchman crawl failed. Retrying once with node crawler. Usually this happens when watchman isn’t running. Create an empty
.watchmanconfig
file in your project’s root folder or initialize a git or hg repository in your project. Error: Watchman error: fileData.mtime_ms.toNumber is not a function. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html. Loading dependency graph, done.Any ideas on what this means and/or how I can fix it?
i simply copied the code from my project, created a new project and pasted there… and it works:) UPDATE: @theapache64 , I guess after i ran “npm audit” and resolved some vulnerabilities after that watchman stopped working in that project and when i created new project, copied the code from previous project and run the packager, it worked (:
it fixed in my solution:
re init react-native project,it will work.
I came across this issue this morning when running Jest on a different machine. I had no idea I had watchman installed. Looking in my usr/local/bin I found out I installed it back in April 2005 along with React-Native when I was experimenting. I will post an issue with watchman in regards to their error message in hopes they will make it less cryptic.
https://github.com/facebook/watchman/issues/428
Would something like “Watchman is installed but not running. Using standard watcher instead.” be less frightening and filled with words I don’t understand? Maybe this is all kind of edge case, but I thought it was worth a mention.
Ah that explains it. 😄
@vjeux Did you previously install RN? @cpojer told me this warning only shows up if: