Closed
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Description
Followed all installation instructions from docs https://facebook.github.io/react-native/docs/getting-started.html#content
platform: windows
version: 7
node: v6.2.0
npm: 3.9.2
react-native-cli: 0.2.0
Error:
This will walk you through creating a new Rea
ct Native project in D:\xampp\htdocs\staging\
tutorials\AwesomeProject
Installing react-native package from npm...
events.js:160
throw er; // Unhandled 'error' event ^
Error: spawn npm ENOENT at exports._errnoException (util.js:953:11)
at Process.ChildProcess._handle.onexit (i
nternal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:3
48:16)
at _combinedTickCallback (internal/proces
s/next_tick.js:74:11)
at process._tickCallback (internal/proces
s/next_tick.js:98:9)
at Function.Module.runMain (module.js:577
:11)
at startup (node.js:160:18)
at node.js:449:3Metadata
Metadata
Assignees
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Activity
perkola commentedon May 24, 2016
+1
Having the same problem. Same setup and versions. Running
react-native init AwesomeProjectas administrator changed nothing.gitlovenotwar commentedon Jun 2, 2016
Any help, please?
gitlovenotwar commentedon Jun 8, 2016
@perkola Have you manage to fix the problem?
joewood commentedon Jun 8, 2016
@gitlovenotwar have you tried using the most recent react-native-cli? It's current on v.1.
gitlovenotwar commentedon Jun 8, 2016
@joewood oh, wow, I don't. Though what's the --save for on global?
P.S. After updating, yes, same error on the one above.
P.P.S. I'm able to start a project by doing the following
react-native init AwesomeProject (This creates a package.json file also gives an error )
npm install react-native --save
react-native android ( add the android package)
react-native run-android (bundle the files)
react-native start
joewood commentedon Jun 8, 2016
Yeah, ignore the --save - not required.
mkonicek commentedon Oct 27, 2016
Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/react-native-init-projectname-hangs-on-windows
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.