-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[BUG] Sometimes package can't be downloaded from the public NPM registry #500
Comments
npm If your bug is preproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo Closing: This is an automated message. |
What / Why
I've recently noticed that some (older?) versions of packages could not be loaded from the public NPM registry sometimes.
For example, p-is-promise@1.0.0 install may return 404 error, which I've traced to the direct curl call:
curl https://registry.npmjs.org/p-is-promise/-/p-is-promise-1.0.0.tgz
When it fails, the returned XML is like:
When
Noticed it today, 2019-11-19.
Where
npm public registry
How
Current Behavior
The issue seems to be a floating bug, it only fails sometimes.
Steps to Reproduce
npm i p-is-promise@1.0.0
or
curl https://registry.npmjs.org/p-is-promise/-/p-is-promise-1.0.0.tgz
Expected Behavior
npm i p-is-promise@1.0.0 should always work.
Who
n/a
References
May be related to (or causing) yarnpkg/yarn#7691
The text was updated successfully, but these errors were encountered: