Problem with init a project on Windows

[xgrommx]

Hi all! I have been tried use react-native for Android on Windows but I got error. This is my steps:

npm i react-native -g
react-native init AwesomeProject

This will walk you through creating a new React Native project in C:\tmp\AwesomeProject
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:429:9)
    at process._tickCallback (node.js:343:17)
    at Function.Module.runMain (module.js:477:11)
    at startup (node.js:117:18)
    at node.js:951:3

[chirag04]

Right now only OSX is supported as stated here: https://facebook.github.io/react-native/docs/getting-started.html#content

[guillaume86]

Using cross-spawn (https://www.npmjs.com/package/cross-spawn) as a replacement for child_process.spawn fixes this particular error.

[xgrommx]

It will be in future?

[mkonicek]

As @chirag04 said, Windows is not supported yet. There are also a few places in the CLI where we call into sh so the error you mention won't be the only one. Windows support would be great but can't promise an ETA yet. Pull request to make the CLI work on Windows are welcome.

The remaining components are the packager and Gradle. Gradle build should work on Windows out of the box. You can try using this example as a template for your app: https://github.com/facebook/react-native/tree/master/Examples/SampleApp

[ide]

Another point I'd like to communicate is that most engineers at FB develop on Macs (w remote Linux server) so those platforms are naturally going to receive more dogfooding within the company. Great Windows support will come from an individual or group of individuals who are passionate to making sure RN runs well on Windows. When the packager is moved to its own repo (happening soon I believe) it should be easier to take in PRs that improve Windows support.

[nanaeasiedu]

I just looked into the code for the react-native-cli and realized it used node.js's default child_process.spawn. I changed this to use shelljs and it worked. Don't know how to get that back into the react-native-cli source on github because after cross-checking, there seems to be some differences in the one on npm and the source code on github.

[kmagiera]

Merging to master task for linux/windows support #2681 let's discuss workarounds there

[BretJohnson]

@kmagiera it looks like you linked back to this issue. Did you mean to link to a pull request instead?

[mkonicek]

The issue is #2693.

[ligboy]

@chirag04 Ubuntu/linux works well......

[leon456]

Wish windows can support ASAP,thanks

[BretJohnson]

FYI - I've been taking a look at getting Windows support to work. It looks like this issue, with "react-native init", no longer happens when I pulled the latest CLI source from github. I'm now trying to get the packager to fully work. I fixed one problem there and am trying to track down the next one.

[martinbigio]

@bret-johnson this might be related to your problem #2789

[BerndWessels]

Hi @mkonicek
I think this issue is back. I get this with the latest master from an hour ago:

Y:\>react-native init hope
This will walk you through creating a new React Native project in Y:\hope
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:429:9)
    at process._tickCallback (node.js:343:17)
    at Function.Module.runMain (module.js:477:11)
    at startup (node.js:117:18)
    at node.js:951:3