Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[npm-issue] packages removed / not available after install #190

Closed
creative-git opened this issue Jun 22, 2017 · 7 comments
Closed

[npm-issue] packages removed / not available after install #190

creative-git opened this issue Jun 22, 2017 · 7 comments

Comments

@creative-git
Copy link

after running "npm i react-native-firebase --save" i get the following message:
**added 31 packages, removed 649 packages and updated 113 packages in 19.899s**

and when i try to run "react-native run-ios", i get "Command run-ios unrecognized"

what am doing wrong ?

@SamMatthewsIsACommonName
Copy link
Contributor

Same here, the install removes all of the react native packages etc for some reason

@Salakar
Copy link
Member

Salakar commented Jun 22, 2017

Hmm this is a weird one - what are your npm versions @barjas @SamMatthewsIsACommonName - this may be a npm v5 issue - can you down grade your npm and give it a whirl - see if it's actually that?

@SamMatthewsIsACommonName
Copy link
Contributor

OK I will do after dinner. My project is now broken again so I need to start a new one. I've been battling cocoapods/ problems with latest react native for last 5 hours straight and about to pull my hair out haha

@Salakar
Copy link
Member

Salakar commented Jun 22, 2017

Looks like other npm 5 users are facing the same issue:

npm/npm#17379
npm/npm#17384

Rollback to 4 for now and you should be good.

@Salakar
Copy link
Member

Salakar commented Jun 22, 2017

Will leave this open for now until the npm issue is resolved.

@Salakar Salakar changed the title Command run-ios unrecognized After installing [npm-issue] packages removed / not available after install Jun 22, 2017
@guhungry
Copy link

Sometimes I have to switch to yarn if npm install have problem (with npm 5.0.3 since it comes with node 8.1.2 by default)

@chrisbianca
Copy link
Contributor

@Salakar according to npm/npm#17384 this was fixed in npm 5.1.0. I've just updated to npm 5.3.0 and everything seemed to work ok, so will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants