-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Won't Run on NPM Start Command #14
Comments
Node conveniently has no documentation around exit code 11, so I'm working a bit blindly here, but 11 is typically associated with segfaults in other contexts. I notice you're running 7.0.0. Do you mind trying to update Node? I know the RN packager had a number of issues with 7.0.0 |
I tried using Node v7.2.1, 6.9.2, neither work. I tried but failed running it on port 3000 as well via: I also get this error, which I'm not familiar with. It may just be junk, I don't know.
|
Hmm, they may be related. Since you're on a Mac, I recommend installing Watchman, as described here: https://facebook.github.io/react-native/docs/getting-started.html Watchman is a much more efficient filesystem watcher than the one that ships in Node, or native solutions like chokidar. It should resolve those file-watching errors, and will definitely make the actually development much faster. |
I'm assuming you've also already tried blowing away the |
I tried blowing away node_modules on 6.9.2 and 7.2.1, and neither worked. I installed Watchman, blew away the node-modules, npm install, and then it didn't crash. I went to the URL http://localhost:8081/vr/ and it loaded. I don't know why that was the solution, but it might be something to add to the documentation for a later note. As of right now I use React.js, not React Native, so didn't think of that. Thanks for the help. |
Thanks, I'll be sure to update the documentation to clarify that we're using the packager from React Native, and probably add a section about Watchman for Mac/Linux users. For the initial documentation, we didn't want the setup process to be too overwhelming, since things should work without Watchman, but it drastically improves the experience. |
thanks @andrewimm , install watchman solve my problem |
Description
Installing app and trying to run using:
react-vr init MyAppName
cd MyAppName
npm start
Expected behavior
Start server
Actual behavior
I get an error:
full npm-debug copy log
Additional Information
The text was updated successfully, but these errors were encountered: