yo react-native-ignite throws "'wc' is not recognized as an internal or external command, operable program or batch file" in Win10 about ignite HOT 10 CLOSED

@Danitk We haven't done any testing on Windows yet. Are you on a Windows Insider build? If not, bash commands won't work on your command line until the general release of the Windows Redstone update this summer, and even then it could be hit-and-miss.

Thanks for bringing this to our attention, but I'm not sure this is something that we'll be able to address in the near future.

from ignite.

Sorry to hear that, hopefully you guys will add Windows support in the future. I'm on Windows 10 Home edition Version 1511 Build 10586.218.

from ignite.

Can you try it from a bash prompt?

Run native Bash on Ubuntu on Windows: In this build, you can natively run Bash in Windows as announced last week at Build 2016. To do this, you first need to turn on Developer Mode via Settings > Update & security > For developers. Then search for "Windows Features" and choose "Turn Windows features on or off" and enable Windows Subsystem for Linux (Beta). To get Bash installed, open Command Prompt and type "bash".

from ignite.

Hey @Danitk - thanks for reporting this!
The wc command is just part of our protection shell script. It's not fundamental to the application running.

Can you do basic react native app initialization with react-native init SomeApp ?

If so, let's see about scheduling a pairing session. @kevinvangelder - this might be a great chance to shine and get ignite legit with Windows.

from ignite.

@GantMan I finally got a chance to try this on my Windows 10 computer and after running npm install --global yo bower grunt-cli and running the generator I got this error:

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open 'D:\Code\IgniteTest\android\app\src\main\AndroidManifest.xml'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at Object.insertInFile (C:\Users\Kevin\AppData\Roaming\npm\node_modules\generator-react-native-ignite\utilities.js:21:27)
    at performInserts (C:\Users\Kevin\AppData\Roaming\npm\node_modules\generator-react-native-ignite\app\index.js:69:13)
    at AppGenerator.end (C:\Users\Kevin\AppData\Roaming\npm\node_modules\generator-react-native-ignite\app\index.js:126:7)
    at C:\Users\Kevin\AppData\Roaming\npm\node_modules\generator-react-native-ignite\node_modules\yeoman-generator\lib\base.js:430:16
    at processImmediate [as _immediateCallback] (timers.js:383:17)

I was then able to run react-native android to generate the missing Android folder, but attempting to run the app resulted in:

:app:preDexDebug
Unknown source file : Error: Could not create the Java Virtual Machine.
Unknown source file : Error: A fatal exception has occurred. Program will exit.

:app:preDexDebug FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:preDexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0_79\bin\java.exe'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 17.426 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

I think I encountered this same error when writing my blog post, I just don't remember how I fixed it off the top of my head, so I'll have to revisit that to see if I can get it working.

TL;DR: Didn't fix anything, but got some additional information we may be able to use to track down the issues.

from ignite.

Interestingly, running ignite new MyProject on OSX automatically detects that yoeman is not installed and installs it where it didn't do that when I was testing on Windows yesterday.

from ignite.

After running:
npm install --global yo bower grunt-cli
then
npm install --global react-native-ignite
then
ignite new MyTestIgniteApp

The app was generated properly.
I had to open the /android folder up in Android Studio as with any react-native project and after that the following worked fine for running the Ignite generated application in the Android emulator using:
react-native run-android

This was on a standard Windows 10 Pro system (1511, build: 10586.420)

from ignite.

@davza Very nice! I'm eager to get Ignite windows friendly now!

Were there any other hiccups?

from ignite.

closing in favor of #196

from ignite.

@GantMan No problems so far.
I generated a signed apk of the base ignite project and it installed fine on my phone.
I'm going to be moving parts my current react-native app into ignite to see how it works and will let you know if I have any problems.

Thanks for the tools :)

from ignite.