-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchman crawl failed. #346
Comments
None of these words make any sense to our users: 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. |
Also the warning links to https://facebook.github.io/watchman/docs/troubleshooting.html which says nothing about how to install Watchman. https://facebook.github.io/watchman/docs/install.html suggests to use I think we need a flag to completely disable this warning/suggestion because it’s optional, and instructions are unfortunately confusing. We can still put instructions on “how to speed up watching” in our Howto. |
cc @cpojer |
I'm a Facebook engineer so watchman is installed on my machine by default ;) |
Ah that explains it. 😄 |
I confirmed that this error is only thrown when using Facebook equipment so I think this isn't actionable and we can close it. I expect FB engineers to figure out how to use watchman, however we might want to improve the error message in Jest to make sure people understand it is no reason to panic. how to repro a non fb-environment: then run |
Thanks for checking. |
For what it's worth, I got this error as well, so it can happen on non-fb equipment. It was because I'd tried jest in the past and ended up with watchman installed on my machine. At least I think that's how I ended up with it. Uninstalling it made the error go away. It would be nice to not ever show this message though. It was cryptic. |
I think we should close this one. I understand the concern but I updated the error message to say to create a |
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. |
The problem is that we have to surface watchman's error and we can't hide how cryptic it is. Maybe create an issue on watchman's bug tracker about improving their error messages? |
I'm a new user to react-native, just got it installed. The documentation seems to be missing the react-native start step and then I noticed the same watchman warning as in this thread (I'm not a facebook engineer |
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. |
Are you a time traveler? 😄 |
Don't tell anyone! Though 2015 sounds better. |
This fixed for me. npm r -g watchman |
Hi @cpojer ,
And it does not work, btw, 'WATCHMAN_CONFIG_FILE=~/watchman' does not look like a command. On the other hand, my situation is:
I would really appreciate if you can help me out. Thank you. |
My error is slightly different: Any ideas on what this means and/or how I can fix it? |
@shireen I am having the exact same error |
@shireen @valetarton I'm running into this issue now. Did ya'll figure out a solution or workaround? I'm on Windows 7. Thanks |
it fixed in my solution:
re init react-native project,it will work. |
Still having this issue. The solutions presented above do not work for me. I tried Vikram's solution and lvlinha's solution. I still see the same error message. I also have created a .watchman file in my project root as instructed by the message, to no avail. UPDATE: Fixed when I did some module upgrades. Not sure what fixed it, but I upgraded to npm ^5.8.0, react ^16.3.0, and expo SDK v26. UPDATE: Nope, it's still happening, but it depends on if I run react-native run-ios as root or not. If I run the simulator as root, I don't get the watchman error, but the packager behaves strangely... very labored. If I don't run it as root, I get the error but the packager runs smoothly and the simulator loads much more quickly. I guess the upgrades didn't help. UPDATE: Fixed by recursively changing the owner of .git to my non-root user. |
After reading all comments and implementing them again getting same error expo: 27.0.1 |
|
i simply copied the code from my project, created a new project and pasted there... |
@theapache64 worked for me too. |
Fixes facebook#346. This is a workaround for a bug in uglifyjs2 (mishoo/UglifyJS#2842), which can cause name collisions when a function with arguments is inlined. This can cause an unintended shadowing of a `var` or `let`, or a `TypeError: Assignment to constant variable` in case of a `const`.
I'm running into this error on master with a project created with
npm run create-react-app ../test
I came up with the "Painless unit testing" sentence. It's now a reality :)
The text was updated successfully, but these errors were encountered: