Ignite: Ignite 2 "New Command" doesn't work

[lacmax]

Ignite 2 "New Command" doesn't work,

When I run the ignite new command only the initial folder is created without any content

What's going on?

Ignite 2 "New Command" doesn't work

Steps to reproduce

ignite new PizzaApp

ignite doctor results:
System
platform darwin
arch x64
cpu 8 cores Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
directory /Users/lucascarvalho/Desktop/ProjetosIgnite

JavaScript
node 7.6.0 /usr/local/bin/node
npm 4.1.2 /usr/local/bin/npm
yarn - null

React Native
react-native-cli 2.0.1

Ignite
ignite 2.0.0-beta.4 /usr/local/bin/ignite

Android
java 1.8.0-ea /usr/bin/java
android home - undefined

iOS
xcode 8.0

[skellock]

do you accidently have react-native installed globally? it should only be react-native-cli. I've seen this environment cause this error.

Try npm rm -g react-native and try again.

[lacmax]

Same problem :( , Last week it was working, I do not know if it was after the last beta version.

[lacmax]

[nonotest]

yep same here, it used to work with beta2 and now fails with beta 4

$ ignite doctor
System
  platform           darwin
  arch               x64
  cpu                8 cores                                          Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz
  directory         ..

JavaScript
  node               7.7.1        /usr/local/bin/node
  npm                4.3.0        /usr/local/bin/npm
  yarn               0.21.3       /usr/local/bin/yarn

React Native
  react-native-cli   2.0.1

Ignite
  ignite             2.0.0-beta.4   /usr/local/bin/ignite

Android
  java               1.8.0_77     /usr/bin/java
  android home       -            /Users/arnaudmoret/Library/Android/sdk

iOS
  xcode              8.2.1

[nonotest]

@lacmax this was related to the project name for me. make sure your project name would be valid if you were using react-native init instead

[fvonhoven]

@lacmax Did you get it working?
@skellock seems to be related to #882 ? Perhaps we can close this if lacmax is 👍

[skellock]

another thing to try is with --npm. this forces yarn to turn off. I've seen a few cases now of conflicts between nvm vs yarn as well as yarn vs yarn. It's hard to keep this straight haha.

[fvonhoven]

@skellock re: yarn...are you saying that people...are getting..."tangled...?"

[jamonholmgren]

@skellock This is labeled "bug" and "help wanted" but I'm not seeing anything actionable here. Good to close?

[skellock]

@lacmax @nonotest can you try this again with the latest? npm i -g ignite-cli.

[nonotest]

It worked the first time after updating ignite-cli.. but then it started not working again.
Looks like it reverted back to the old behaviour although I still have

$ ignite -v
2.0.0-beta.8

Will try to re-install ignite later and see what happens.
Cheers,