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

URIjs fails with bad hash #2508

Closed
Marius-Stroe opened this issue Jun 9, 2017 · 2 comments
Closed

URIjs fails with bad hash #2508

Marius-Stroe opened this issue Jun 9, 2017 · 2 comments

Comments

@Marius-Stroe
Copy link

Marius-Stroe commented Jun 9, 2017

I can't create or use a react app anymore as create-react-app fails with the following message:

...
Installing packages. This might take a couple minutes.
Installing react, react-dom, and react-scripts...

yarn add v0.20.0
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning react-scripts > sw-precache-webpack-plugin > sw-precache > dom-urls > URIjs@1.16.1: package renamed to "urijs" (lower-case), please update accordingly
[2/4] 🚚  Fetching packages...
error https://artifactory.twitter.biz:443/api/npm/js-virtual/URIjs/-/URIjs-1.16.1.tgz: Bad hash. Expected "edebc678b8b74b26b05d2b481e12383f5ae04b8b" but got "859ad31890f
5f9528727be89f1932c94fb4731e2"
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command...

See entire npm-debug.log

It suddenly started happening when creating a simple react app. Any help would be appreciated as I can't do anything right now: can't install any package.json dependencies.

Thanks!

I've also submitted a bug with npm, as the error message suggests that: npm/npm#17108

@Timer
Copy link
Contributor

Timer commented Jun 9, 2017

Based on your console output, this is a bug with yarn -- not npm.
Please upgrade your yarn version to the latest.

It may not be a bug at all, however. It looks like you're using a custom registry which is corrupting packages or providing invalid hashes.

Can you try switching back to the default registry?

@Marius-Stroe
Copy link
Author

Marius-Stroe commented Jun 10, 2017

@Timer , you're right. Switched to default registry (was using the one at work inadvertently) and it worked. Thanks!

@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants