Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Just trying this out but doesn't work following readme.

See original GitHub issue

Excited to try out Following Steps…

Step 1: Install

npm install -g react-native-ignite
.
.
Yeoman Doctor
Running sanity checks on your system

✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version

Everything looks all right!

> react-native-ignite@1.8.0 postinstall /Users/toddpickell/.nvm/versions/node/v6.6.0/lib/node_modules/react-native-ignite
> npm i -g generator-react-native-ignite

> spawn-sync@1.0.15 postinstall /Users/toddpickell/.nvm/versions/node/v6.6.0/lib/node_modules/generator-react-native-ignite/node_modules/spawn-sync
> node postinstall

Looks good lets see the magic…

Step 2: Use

~/code ᐅ ignite new IgniteTestApp
🔥 Setting IgniteTestApp on FIRE! 🔥
? ==========================================================================
We're constantly looking for ways to make yo better!
May we anonymously report usage statistics to improve the tool over time?
More info: https://github.com/yeoman/insight & http://yeoman.io
========================================================================== No
Error react-native-ignite IgniteTestApp

You don't seem to have a generator with the name react-native-ignite installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 1 registered generators run yo with the `--help` option.

Not sure what happened there. I have never used Yo before so I am not familiar but it looks like it installed the generator in the initial install part. Am I missing some assumed knowledge here or is the readme out of date?

Hiya! So you think it’s broken or missing a feature eh?

Welllllll, it just might be. Do me a favor and check the following.

Issue does not already exist
searched didn’t find an open issue for this.
Identify exactly what aspect your issue is about
- ignite base application
- ignite the cli
- ignite generated code

Also, for the quickest assistance please run ignite doctor and paste in everything (including the lines with 3 backticks).

Computer
  Platform: darwin

Ignite
  Version: 1.8.0
  Path: /Users/toddpickell/.nvm/versions/node/v6.6.0/bin/ignite

Node
  Version: v6.6.0
  Path: /Users/toddpickell/.nvm/versions/node/v6.6.0/bin/node

NPM
  Version: 3.10.3
  Path: /Users/toddpickell/.nvm/versions/node/v6.6.0/bin/npm

Yeoman
  Version: 1.5.0

React Native CLI
  Version: 1.0.0

App
  React Native Version: ¯\_(ツ)_/¯

Issue Analytics

State:
Created 7 years ago
Comments:22 (8 by maintainers)

Top GitHub Comments

2reactions

skellockcommented, Nov 23, 2016

FWIW. I always install the build tools 23.0.1, 23.0.2, and 23.0.3.

React Native released a few versions where the moved to 23.0.3. 3rd party folk then moved up too. Then RN moved back to 23.0.2. But didn’t go back. Meanwhile some 3rd party folk never moved from 23.0.1.

And hilarity ensued.

1reaction

GantMancommented, Nov 26, 2016

Sorry for the difficult setup @eikebartels - we will continue to try to add checks in place to help users, but sometimes the issue is so elusive, we can’t even conceive what a friendly warning would check for.

Fortunately it appears you’re up and running for now. Please ping us if you have any issue.