-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Unable to start react-native package manager #10188
Comments
Check this https://gist.github.com/DanHerbert/9520689 |
Some times getting below error message when run the command react-native start DemoWebBridge$ react-native start [10/5/2016, 6:53:12 PM] Building Dependency Graph React packager ready. ERROR watch /home/tulasiram/AndroidStudioProjects/DemoWebBridge/node_modules/fbjs/node_modules/core-js/fn/regexp ENOSPC See http://facebook.github.io/react-native/docs/troubleshooting.html Using react-native version 0.34.1 |
Got the solution run below command to solve the issue using the following command in a terminal window we can simply increase the limit echo fs.inotify.max_user_watches=582222 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p For Arch Linux add fs.inotify.max_user_watches=524288 to /etc/sysctl.d/99-sysctl.conf and then execute sysctl --system. This will also persist across reboots. {source stackoverflow} |
How do you solve this problem? I really don't know what's going on here, can you help me? |
@chachaxw are you able to run the react naive package manager. |
@tulasi-ram I have solved this problem. I forgot install watchman |
Looks like this is solved? Feel free to re-open or file a new issue if there are still problems starting the packager with newer versions of RN. |
I am experiencing this error after updating to OSX Sierra and installing Xcode 7.3. Prior to the update I had Yosemite and Xcode 7.2. Any suggestions on how to resolve this? |
Thank. You. So. Much. |
@iboxgithub, what is the fix? Would you mind submitting a pull request for it? |
Hi, actually I just used the workaround, that's why I let a message for FB devs. |
Ha... you are a FB dev...my comment looks weird now 🥇 |
No worries, all of us at FB are just people! Maybe you could add this workaround to the troubleshooting page? http://facebook.github.io/react-native/releases/next/docs/troubleshooting.html#content |
Following @ericvicenti request on facebook#10188 (comment) Hope it helps
Done, with some explanation in order to understand why this happens, let me know if it is ok |
Summary: Following ericvicenti request on #10188 (comment) Hope it helps Thanks for submitting a pull request! Please provide enough information so that others can review your pull request: > **Unless you are a React Native release maintainer and cherry-picking an *existing* commit into a current release, ensure your pull request is targeting the `master` React Native branch.** Explain the **motivation** for making this change. What existing problem does the pull request solve? Prefer **small pull requests**. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. **Test plan (required)** Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. Make sure tests pass on both Travis and Circle CI. **Code formatting** Look around. Match the style of the rest of the codebase. See also Closes #12578 Differential Revision: D4682076 Pulled By: mkonicek fbshipit-source-id: 2fab5355a066eb3d8333e50f07ab3a258cbc002b
Summary: Following ericvicenti request on #10188 (comment) Hope it helps Thanks for submitting a pull request! Please provide enough information so that others can review your pull request: > **Unless you are a React Native release maintainer and cherry-picking an *existing* commit into a current release, ensure your pull request is targeting the `master` React Native branch.** Explain the **motivation** for making this change. What existing problem does the pull request solve? Prefer **small pull requests**. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. **Test plan (required)** Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. Make sure tests pass on both Travis and Circle CI. **Code formatting** Look around. Match the style of the rest of the codebase. See also Closes #12578 Differential Revision: D4682076 Pulled By: mkonicek fbshipit-source-id: 2fab5355a066eb3d8333e50f07ab3a258cbc002b
I keep getting the below when trying to run
npm start
:Why am I getting this? I"m using below versions:
The text was updated successfully, but these errors were encountered: