Cli: npm ERR! 404 Not Found - GET https://registry.npmjs.org/@react-native-community%2fcli - Not found

Created on 6 Aug 2020  路  14Comments  路  Source: react-native-community/cli

Environment


npm ERR! 404 Not Found - GET https://registry.npmjs.org/@react-native-community%2fcli - Not found
npm ERR! 404
npm ERR! 404 '@react-native-community/cli@^4.7.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'react-native'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Description

npx react-native init command not working and giving error that react native community cli is not found

Reproducible Demo

initialize a new react-native project

bug report

Most helpful comment

Working but still exploding on required packages in my case (using typescript template)

  • "@typescript-eslint/eslint-plugin@^2.25.0",
  • "@typescript-eslint/parser@^2.25.0"

All 14 comments

Same problem!
I can't complete the update of React Native because I can't update React native CLI because of this error

Same problem from "npm i @react-native-community/....."

Same, can't upgrade RN to latest version

It seems to be a global problem with scoped packages installation from NPM registry :

https://status.npmjs.org/

Guess we'll just wait for them to fix this problem :shrug:

I have the same issue with the 3.0.0 version

Same issue! Hope it gets fixed soon :)

same here. I can't create new project

Vendor lock! https://status.npmjs.org/ Issue with npm

Working now.

Working but still exploding on required packages in my case (using typescript template)

  • "@typescript-eslint/eslint-plugin@^2.25.0",
  • "@typescript-eslint/parser@^2.25.0"

Working but still exploding on required packages in my case (using typescript template)

* "@typescript-eslint/eslint-plugin@^2.25.0",

* "@typescript-eslint/parser@^2.25.0"

Same here, seems like it's still re-caching packages and maybe it didn't arrive to those yet.
However the one of the issue is already fixed.

Working but still exploding on required packages in my case (using typescript template)

* "@typescript-eslint/eslint-plugin@^2.25.0",

* "@typescript-eslint/parser@^2.25.0"

Same here, seems like it's still re-caching packages and maybe it didn't arrive to those yet.

Yeah, I tried just now but it seems that the cache is broken again as I am getting an error on "@react-native-community/cli@^4.7.0" xD Fingers crossed馃馃徎

Working but still exploding on required packages in my case (using typescript template)

* "@typescript-eslint/eslint-plugin@^2.25.0",

* "@typescript-eslint/parser@^2.25.0"

Same here, seems like it's still re-caching packages and maybe it didn't arrive to those yet.

Yeah, I tried just now but it seems that the cache is broken again as I am getting an error on "@react-native-community/cli@^4.7.0" xD Fingers crossed馃馃徎

馃槄 Haha that was unexpected, thanks for the heads up..

Caused by npm outage, closing

Was this page helpful?
0 / 5 - 0 ratings