-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
package 404 not found #1626
Comments
The same |
It seems it cannot find all the scoped packages. |
Same here. |
Same here, all vue cli packages for example are 404ing |
I'm having this problem too |
same here |
I believe there's another issue that is similar Duplicate of #1624 |
Facing the same. even using npm install getting the same error |
same here |
Confirm. |
Even if it states its resolved partly, here you get another hint to follow: Not Found - GET https://registry.npmjs.org/@protobufjs%2fbase64 - Not found |
+1 we're waiting for your resolved npm team! hang in there✌️ |
same |
same. |
we can only wait for resolve issues |
same |
An unexpected error occurred: "https://registry.yarnpkg.com/@react-navigation/stack/-/stack-5.2.10.tgz: Request failed "404 Not Found"". |
Same! Unable to init a new Angular project... |
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@material-ui%2fcore - Not found |
any solution time? screwed in the middle of a production deployment. Any scoped npm package is failing |
now ,its fixed |
Still not fixed for me! |
This is critical error. No scoped packages can be downloaded. |
No it's not |
same here, 404 on everything scoped |
Same here, almost for an hour for now. |
Getting this on many dozens of unrelated packages, many of which are dependencies of some major projects. In case there is some region CDN issue, I tried using a VPN to appear to be in a different continent but that didn't make any difference. Sometimes a package is present but is not the latest released but one from a long time ago. Sometimes a package is not present. Tried various tricks like changing NPM version, npm config set registry http://registry.npmjs.org, etc. but no luck. Does appear to be a registry issue. Am dead in the water on all my projects right now and no longer able to install packages like Cordova for example. |
@NeilCresswell it's an issue in the registry. See here: https://status.npmjs.org/ |
@korki43 Thanks. I saw your post above right after I submitted mine and have added status.npmjs.org to my bookmarks. |
ok i'm not alone.... |
The big day when deploy is not available) |
This reminds me last year.. Maybe it was almost this season, wasn't it?? |
same here, |
Yes, I Have same issue |
Same problem here |
Latest update! they're continuing to work on a fix for this issue: https://status.npmjs.org/incidents/cksjqc1w11v5 |
I didn't find many NPM registry alternatives but while this is not fixed I am using this one:
|
Same problem here |
Same problem. Can't install creat-react-app and create-next-app because of it |
I think it's fixed ( at least in my case) |
fixed for me too |
Already working! THANK YOU! |
Yes, working! tks! |
I still have the issue:
|
I still have the issue with AWS amplify builds. |
Of note, a 404 response is not uncommon to experience when there is a misconfiguration in your env & you're making requests to private/scoped packages; That said, this issue seemed to occur during a partial outage back in August, so I'm going to assume this has been resolved for the bulk of folks since that incident, & close accordingly. If you continue to experience any issues with the npm registry, website or any other service in the future, please...
If everything looks right & you've still got issues/errors, you can file a ticket here: https://www.npmjs.com/support This repo's issues are meant to capture bugs within the |
What / Why
Your package manager couldn't get any packages. (404 not found)
When
Now
Where
How
Current Behavior
404 not found
The text was updated successfully, but these errors were encountered: