-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
error watching file exception, preventing npm start from working + fix #520
Comments
PRs for documentation are always welcome. 😀 |
Didn't read the fix in SO. Actually, I think the watchman fix has been mentioned/documented elsewhere. @kylewelch? |
Had the same problem, and the fix was to install watchman, like described here facebook/create-react-app#2393 |
Whoever would like to PR for the docs, feel free to do so. I think @kwelch had planned on doing this, #469 (comment), but I think he got busy. Kyle? |
I'm a github n00b, but I'd be happy to make something like this my first github PR. :) |
Sounds good @polaire801. Hit me up if you need a hand |
On Mac OS High Sierra had this problem. Reinstalling watchman with brew solved the problem apropos expo/create-react-native-app#281 |
Closing this as it was documented in #536. |
This appears to be similar to issue #437, which was closed, but I just experienced the same issue on a new mac (today, 12/23/17). I vaguely recall running into this issue on another machine a few months ago (also mac).
I followed the installation instructions and troubleshooting section, but would run into an error when executing 'npm start -s'.
I searched on the error text and found this article that mentions the error and suggests a fix.
https://stackoverflow.com/questions/39675840/error-watching-file-for-changes-emfile-when-run-the-examples-from-facebook-re
at the very least, I think it would be helpful to include a bullet point in the README's troubleshooting section for this issue.
if it helps..
npm version: 5.6.0
node version: 9.3.0
os: mac high sierra 10.13.2
Thanks!
The text was updated successfully, but these errors were encountered: