React-native: Cannot find module 'invariant' - react-native-cli

Created on 6 Dec 2016 · 25Comments · Source: facebook/react-native

Description

When trying to create a new react-native project there an error while installing packages.

Reproduction

react-native init

Additional Information

React Native version: react-native-cli: 1.0.0
Operating System: macOS Sierra 10.12.1

Locked

Source

frnk94

👍11

Most helpful comment

Same issue here. I tried herudi's solution and still got the same error, but it worked after updating npm to the latest version (npm install npm@latest -g).

Old npm version: 2.15.8
New npm version: 4.0.3

skonves on 7 Dec 2016

👍39 🎉9

All 25 comments

11324 Related ?

frnk94 on 6 Dec 2016

Reproduced over here too. Trying to init a new project.

Cfiddle on 6 Dec 2016

Same error with me.
Cannot find module 'invariant'

herudi on 7 Dec 2016

We get it as well when "running" the react-native Examples (latest master) in Xcode.

react-native-cli: 1.3.0
macOS Sierra: 10.12.1

... but only on one of our machines (the other is fine with the same versions).

Fixed it here by running npm i --save-dev invariant on the react-native cloned repo, which is obviously a temporary solution, and I doubt that would work with the CLI.

node: v4.4.7
npm: 2.15.8

And we get no problem with the actual cli init command!

haustraliaer on 7 Dec 2016

👍8

work for me.
npm cache clean
npm uninstall react-native-cli -g
npm install react-native-cli -g
react-native init myapp

herudi on 7 Dec 2016

👍25

+1 :S

nuthinking on 7 Dec 2016

Same issue here. I tried herudi's solution and still got the same error, but it worked after updating npm to the latest version (npm install npm@latest -g).

Old npm version: 2.15.8
New npm version: 4.0.3

skonves on 7 Dec 2016

👍39 🎉9

npm cache clean
npm uninstall react-native-cli -g
npm install react-native-cli -g
react-native init myapp

It worked for me but it installed package dependencies through yarn v0.16.1

frnk94 on 7 Dec 2016

Like skonves, I updated npm to 4.0.3 and tried herudi's solution. No luck for me, but I was able to get it working by just installing invariant globally. Kinda hacky, but it works for me.

npm install -g invariant

rogueSnake on 7 Dec 2016

Like haustraliaer, npm i --save-dev invariant worked for me.

Cfiddle on 7 Dec 2016

👍20 🎉4 😄1

npm i --save-dev invariant worked for me

devangpandya20 on 8 Dec 2016

👍4

skonves solution worked for me

gnanaprakash on 9 Dec 2016

@skonves npm install npm@latest -g solution works for me.

zerocoolys on 16 Dec 2016

👍2

npm i --save-dev invariant work for me.

Tim77277 on 23 Dec 2016

@herudi +1

@skonves +1 for figuring that older NPM versions have an issue here great job :)

Nopzen on 23 Dec 2016

This worked for me:
```- npm cache clean

npm uninstall react-native-cli -g
npm install npm@latest -g
npm install react-native-cli -g
react-native init myapp```

malcriad0 on 16 Jan 2017

👍3

upgrade npm works for me ,thanks a lot~

WeIio on 23 Jan 2017

@skonves also worked for me, thanks!

mrsimonfletcher on 26 Jan 2017

@skonves npm install npm@latest -g solution works for me.

antonis80 on 9 Feb 2017

Upgraded npm then follow @herudi commands worked for me.

- npm install npm@latest -g
- npm cache clean
- npm uninstall react-native-cli -g
- npm install react-native-cli -g
- react-native init myapp

kythanh on 14 Feb 2017

@skonves It worked for me too,thanks

NineCity on 17 Feb 2017

npm i --save-dev invariant
works for me

sumitk on 26 Mar 2017

Upgrading npm with npm install npm@latest -g fixed for me.

Noitidart on 3 Jul 2017

A note for anyone getting this issue with anymatch not being found.

Doing a npm i --save-dev anymatch fixes the problem. Seems like this may work for a few packages not being found.

brobey8 on 4 Jul 2017

👍2

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.