Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Yarn appears to be fetching for a wrong repository : https://registry.yarnpkg.com/react-native-template-react-native-template-typescript
See original GitHub issueBug
Initializing a projet with command :
npx react-native init project --template react-native-template-typescript
Returns an error:
error An unexpected error occurred: “https://registry.yarnpkg.com/react-native-template-react-native-template-typescript: Not found”.
Environment info
react-native version: 0.61.3 CLI: @react-native-community/cli yarn: 1.19.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:10
Top Results From Across the Web
There appears to be trouble with your network connection ...
One of my dependencies (react-native itself) had the wrong value and it got stuck there. Took me a while to realize because it...
Read more >Yarn - There appears to be trouble with your network ...
This happens when your network is too slow or the package being installed is too large, and Yarn just assumes it's a network...
Read more >yarn could not resolve host registry.yarnpkg.com - Alex Hudson
So, the failure mode I'm talking about looks like this: $ yarn install yarn install v1.21.1 info No lockfile found.
Read more >Publishing a Package - Yarn
When you publish a package with Yarn it goes onto the npm registry which is used to distribute packages globally. Logging into npm....
Read more >Yarn publish does not work (#121668) · Issues - GitLab
A yarn publish fails with a 404 when attempting to publish a package to the NPM registry. This looks it may be more...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Mnjaro
I have the same issue. But I fix it by:
In new version of cli you can see ASCII React logo
Yes, I had to do this, with npx doesnt work for me.
Thanks