React-native: npm start doesn't work after upgrade to 0.15.0

[Bhullnatik]

npm start stopped working after upgrading to React-Native 0.15.0 yielding:

> [email protected] start Dev/tmp/AwesomeProject
> react-native start

Looks like you installed react-native globally, maybe you meant react-native-cli?
To fix the issue, run:
npm uninstall -g react-native
npm install -g react-native-cli

Output of npm -g list --depth=0:

/usr/local/lib
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Output of npm list --depth=0:

[email protected] Dev/tmp/AwesomeProject
└── [email protected]

To be noted, using react-native start works as expected, which make me think this is a npm bug but I'm not sure on how to get started.

[facebook-github-bot]

Hey Bhullnatik, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

• If this is a feature request or a bug that you would like to be fixed by the team, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
• If you don't know how to do something or not sure whether some behavior is expected or a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
• We welcome clear issues and PRs that are ready for in-depth discussion; thank you for your contributions!

[ahanriat]

Related to http://stackoverflow.com/questions/33908314/packager-wont-start

[radko93]

Try adding react-native-cli to your (dev) dependencies.

[ahanriat]

It works perfectly ! Thanks @radko93

[Bhullnatik]

Thanks, this works but is it the expected behavior? Shouldn't react-native-cli be installed globally? Why the change in the 0.15.0?

[ide]

npm 3 might have broken global lookup of modules from npm run-scripts (I haven't verified... just a guess)

[Bhullnatik]

@ide That's what my first thought was, but under the same node/npm configuration it works with React-Native 0.14.0, while it doesn't with the 0.15.0+.
I would be interested in fixing this myself, but I don't know where to begin looking.

Thanks for your answer.

[radko93]

It's not npm 3 case, I've tested it on npm v2 and archieved the same problem.

[grimen]

Ran into the issue, resolved after plenty of head scratching by cleaning node_modules (rm -rf ./node_modules) and then upgrading NPM (npm install npm -g) and install deps in the generated React Native project (npm install). Upgrade clash I guess, didn't have this issue last week.

[exoer]

Solved on Stackoverflow http://stackoverflow.com/questions/33908314/packager-wont-start

[xxmyjk]

http://stackoverflow.com/questions/33908314/packager-wont-start, the following helps me

  "scripts": {
    "start": "$NVM_BIN/react-native start"
  }

[GantMan]

:+1: adding cli as a dependency worked for me for android deploys

[GantMan]

Something went fishy with today's build. I had to:
npm un react-native-cli and npm i react-native-cli
FYI for others.

[muratsu]

@GantMan same thing happened to me too. Reinstalling react-native-cli once you update react-native solves the problem as you mentioned.

[madhums]

Adding react-native-cli to dev-deps doesn't solve the issue. What is the real issue here?

"react-native": "0.19.0",
"react-native-cli": "~0.2.0"

$ node -v 
v6.1.0
$ npm -v 
3.8.6

[madhums]

After npm install,

$ ls -l node_modules/.bin/react-native
lrwxr-xr-x  1 madhu  staff  47 May 17 15:04 node_modules/.bin/react-native -> ../react-native/local-cli/wrong-react-native.js

[madhums]

Ah, nevermind

npm un react-native-cli -D
npm un react-native-cli -g
rm -rf node_modules
npm cache clear
npm i
npm i react-native-cli -D

and then it works. Weird !!