Cli: npm is down

We're also receiving erroneous 404's from a variety of packages, different package each time...

npm ERR! code E404

Hi,

We're also having the same problem with the following package: https://www.npmjs.com/package/@nestjs/typeorm. We cannot access this package on the site and via npm install.

The following shows on the website:

ESOCKETTIMEDOUT

id: 72632f72-98ce-441b-80ac-335af76b4766

The following shows on our CI/CD:

npm ERR! 404 '@nestjs/[email protected]' is not in the npm registry.

MS :trollface:

Same here, 403 and 404 errors

MS :trollface:

Just wait. GitHub is also MS, so … :trollface:

maybe you forgot to renew your npm subscription :trollface:

MS :trollface:

Just wait. GitHub is also MS, so … :trollface:

Soon TikTok will join the squad. :trollface:

Heh, I can't run CI jobs on my project at work because of this(

Heh, I can't run CI jobs on my project at work because of this(

Join the queue

same issue

idem

Heh, I can't run CI jobs on my project at work because of this(

so I pushed node_modules to github lol

Same here :)

https://status.npmjs.org/

Update - The ongoing issue may also affect installation of scoped packages. We continue investigating these issues.
Aug 6, 08:55 UTC

https://status.npmjs.org/

Update - The ongoing issue may also affect installation of scoped packages. We continue investigating these issues.
Aug 6, 08:55 UTC

For me https://status.npmjs.org/ is down

same issue

https://registry.npmjs.org/...-> registry responds with 404

https://www.npmjs.com/package/.... -> dashboard responds with ESOCKETTIMEDOUT

+1

This couldn't have happened at a better time for me.... 🤦‍♂️
Someone call IT, tell them to turn it off and on again

Any news whats going on? When is it getting resolved?

Latest news from npm: https://status.npmjs.org/

We have identified the problematic component and the team is working on a fix.
Aug 6, 09:09 UTC

Getting 404's as well: npm ERR! 404 Not Found - GET https://registry.npmjs.org/@polka%2furl - Not found

Same here

(base) ohadchaet@Ohads-MacBook-Pro main % npm i -g firebase-tools
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@google-cloud%2fpubsub - Not found
npm ERR! 404 
npm ERR! 404  '@google-cloud/pubsub@^1.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 'firebase-tools'
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ohadchaet/.npm/_logs/2020-08-06T09_29_56_322Z-debug.log
(base) ohadchaet@Ohads-MacBook-Pro main % 

Ditto, builds with Angular is also failing, with @angular-devkit/build-angular.

$ npm i @angular-devkit/build-angular
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@angular-devkit%2fbuild-angular - Not found
npm ERR! 404
npm ERR! 404  '@angular-devkit/build-angular@~0.1000.5' 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
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\User\AppData\Roaming\npm-cache\_logs\2020-08-06T09_35_02_319Z-debug.log

Latest news from npm: https://status.npmjs.org/

Update - The issue with the npm website was resolved. We are still looking into error telemetry for installation of scoped packages but are seeing signs of improvement.
Aug 6, 09:33 UTC

Heh, I can't run CI jobs on my project at work because of this(

so I pushed node_modules to github lol

The same :)

Same for @hapi/bourne@latest

Same for @rollup/pluginutils

still not work...

still not work...

just keep an eye on the status page https://status.npmjs.org/
latest update just a moment ago, they are making some progress with the faulty cache

Errors are decreasing while we re-populate a faulty cache. We are working to speed up that process to fully resolve the remaining issues quickly.

@egoroof update your post with the status page link, save people just posting me toos
here - https://status.npmjs.org/

@egoroof update your post with the status page link, save people just posting me toos

done

yaa, im not alone

hm, subscribing to this page for a new portion of memes

Same for @yarnpkg/lockfile

Same for @nestjs/common

same for @webpack-contrib/schema-utils

same for @material-ui/core

Random packages are failed

same here.

Are there any registry mirrors we can use?

Are there any registry mirrors we can use?

You can try taobao: yarn install --registry=https://registry.npm.taobao.org

We replaced the faulty cache and our telemetry indicates a significant improvement in error rates. We'll continue to monitor the situation and make sure all issues are fully resolved.
Aug 6, 11:36 UTC

https://status.npmjs.org/

back up and running. thank you

yes, it works now for me.

yarn install finished without errors!

Done in 250.75s.

Done in 250.75s.

try npm ci :)

Ladies and gentlemen, it's alive!

mark

It 's working !!!!

more than 3.5 hours of outage - cool uptime

I still see the problem:
```
npm i @tuxc/long
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tuxc%2flong - Not found
npm ERR! 404
npm ERR! 404 '@tuxc/long@latest' 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
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
````

@egoroof Agreed, leaving us without CI/CD for 3.5 hours is ridiculous. This problem has been resolved however and if you're experiencing issues I'd give it another 30 minutes or so

Still waiting.

https://status.npmjs.org/incidents/cksjqc1w11v5?u=clfvn2m9yb5p
this is considered as resolved @wildmichael

Well, it ain't for me:

$ npm i @tuxc/long
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tuxc%2flong - Not found
npm ERR! 404
npm ERR! 404  '@tuxc/long@latest' 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
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

I don't see any trace of a @tuxc/long package on npmjs.com.
My guess is that this is another issue, may be should you search for a replacement package (long ?).

Guys please check detailed info about today outage, don't spam here: https://status.npmjs.org/incidents/cksjqc1w11v5

Thanks for being patronizing. Where else should I complain that the issue isn't fixed for this package then? Because the "detailed info" doesn't allow me to provide any feedback.

@otonck this particular package is a transitive dependency somewhere in angular, not my choice.

@wildmichael ok, i guess you just mistyped the package name (should be xtuc and not tuxc from angular's yarn.lock)

Banging my head against the wall. Very sorry for the noise.

:trollface:

npm i firebase npm ERR! Response timeout while trying to fetch http://registry.npmjs.org/firebase (over 30000ms)

The same issue with firebase.

:trollface: