ignite new testApp misses react-native-cli despite it being installed

I installed the react-native-cli and did a react-native init testApp followed by react-native run-ios and all the world was good 😃

Then I cd ~ && npm install react-native-ignite -g followed by ignite new testApp which had me left with this:

$ ignite new testApp
This command requires yo to be installed.
Installing yo...
(node:55281) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
/Users/walther/.node/bin/yo-complete -> /Users/walther/.node/lib/node_modules/yo/lib/completion/index.js
/Users/walther/.node/bin/yo -> /Users/walther/.node/lib/node_modules/yo/lib/cli.js

> yo@1.8.5 postinstall /Users/walther/.node/lib/node_modules/yo
> yodoctor


Yeoman Doctor
Running sanity checks on your system

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

Everything looks all right!
/Users/walther/.node/lib
└── yo@1.8.5 

🔥 Setting testApp on FIRE! 🔥
-----------------------------------------------
  (                  )   (                   
  )\ )   (        ( /(   )\ )    *   )       
 (()/(   )\ )     )\()) (()/(  ` )  /(   (   
  /(_)) (()/(    ((_)\   /(_))  ( )(_))  )\  
 (_))    /(_))_   _((_) (_))   (_(_())  ((_) 
 |_ _|  (_)) __| | \| | |_ _|  |_   _|  | __|
  | |     | (_ | | .` |  | |     | |    | _| 
 |___|     \___| |_|\_| |___|    |_|    |___|
-----------------------------------------------

An unfair headstart for your React Native apps.
https://infinite.red/ignite

-----------------------------------------------
Igniting testApp

𝗫 Missing react-native - 'npm install -g react-native-cli'
$ npm list react-native-cli
/Users/walther
└── react-native-cli@1.0.0 

$ 

Finally I tried to verify that the react-native-cli was actually there - which npm list react-native-cli seems to support ? So now I’am at a loss as to what next, debugging-wise?

Oh - and ignite doctor tells me this:

$ ignite doctor
/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/ramda/dist/ramda.js:4307
                return str.trim();
                          ^

TypeError: Cannot read property 'trim' of null
    at Object.trim (/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/ramda/dist/ramda.js:4307:27)
    at Object.f1 [as trim] (/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/ramda/dist/ramda.js:446:27)
    at Command.<anonymous> (/Users/walther/.node/lib/node_modules/react-native-ignite/index.js:116:36)
    at Command.listener (/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/commander/index.js:301:8)
    at emitTwo (events.js:106:13)
    at Command.emit (events.js:191:7)
    at Command.parseArgs (/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/commander/index.js:615:12)
    at Command.parse (/Users/walther/.node/lib/node_modules/react-native-ignite/node_modules/commander/index.js:458:21)
    at Object.<anonymous> (/Users/walther/.node/lib/node_modules/react-native-ignite/index.js:133:21)
    at Module._compile (module.js:541:32)
$ 

[wdiechmann]

well - Steve

it’s as if you’re psychic 😃

did a quick

$ more ~/.bash_profile #!/usr/bin/env bash

echo ‘.bash_profile start’

PATH additions --------------------------

mysql

PATH=“/usr/local/mysql/bin:$PATH”

npm

PATH="/usr/local/share/npm/bin:~/.node/bin:$PATH” —snip—

and for good measure

$ more ~/.bashrc

System-wide .bashrc file for interactive bash(1) shells.

export PS1='$ ’

Make bash check its window size after a process completes

shopt -s checkwinsize

export PATH=$HOME/local/bin:$PATH

PATH=$HOME/local/bin:$HOME/bin:$HOME/.node/bin:$PATH

I did the .bashrc ‘add-on’ - but the .bash_profile was sitting there all the time! This is an important lesson (even with 20 years of *nix under my belt - most of which were decent scripting, bashing, etc - but it never crossed my mind to distinguish between the two SOG’s) 😉

cheers, Walther

Den 6. sep. 2016 kl. 16.02 skrev Steve Kellock [e-mail]:

Indeed. For closure, I’d love to know how the shell knows, but a script doesn’t. I wonder if perhaps the PATH was inside .bash_profile instead of .bashrc originally?

That might explain it.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

{“api_version”:“1.0”,“publisher”:{“api_key”:“05dde50f1d1a384dd78767c55493e4bb”,“name”:“GitHub”},“entity”:{“external_key”:“github/infinitered/ignite”,“title”:“infinitered/ignite”,“subtitle”:“GitHub repository”,“main_image_url”:“https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png",“avatar_image_url”:“https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png”,“action”:{“name”:"Open in GitHub”,“url”:“https://github.com/infinitered/ignite"}},“updates”:{“snippets”:[{“icon”:“PERSON”,“message”:"@skellock in #354: Indeed. For closure, I’d love to know how the shell knows, but a script doesn’t. I wonder if perhaps the PATH was inside .bash_profile instead of .bashrc originally? \r\n\r\nThat might explain it.\r\n”}],“action”:{“name”:“View Issue”,“url”:“https://github.com/infinitered/ignite/issues/354#issuecomment-24495 9568”}}}

[wdiechmann]

Actually - I woun’t 😃

What I did was ponder - and then I added $HOME/.node/bin to my PATH!

That helped ignite along - and everybody may now return to their stations and have a biscuit and a cup’o’tea 😄

Sorry for all the commotion