Yes, I'm having the same issue. Getting 404 for React 19 [0].

However, according to npm's status page [1], there's a scheduled maintenance occurring right now, so that's expected.

[0] https://www.npmjs.com/package/react/v/19.0.0

[1] https://status.npmjs.org

Not sure why they can't return a more appropriate HTTP code.

Yes. any package I check is a 404 at the moment. Seems related to the scheduled maintenance mentioned here: https://status.npmjs.org/

Seems like 404 is unexpected behaviour, according to the maintenance notes:

> While some features will remain operational, like installations and search, minor inefficiencies may occur.

Apparently there's scheduled maintenance ongoing - but it wasn't supposed to break everything :) https://status.npmjs.org/

I'm having the same issue, although it seems to be intermittent/recovering. Some packages I saw 404s on seem to be coming back.

Same. Turns out there's a planned maintenance, don't know if they intended to break installations though.

Thanks for posting. I was confused as hell why I couldn't install Axios and I was getting a 404 earlier.

It seems to be back up for me.

The sunday on call devs at NPM are probably scrambling

just ran into the third pretty common package that i can't update due to a 404, stuff that is pretty well maintained

Oh no! Anyway...

Having the same issue over here in Germany.

I have installed a package, it works

Having the same issue

Yes multiple 404s

Same.

so what's next?

Behaving like a professional and installing Artifactory to never have this issue again?

This site is hilariously fucked on mobile https://jfrog.com/artifactory

I've switched to hand coding all my dependencies from scratch for today.

You switched to C?

C is too abstract, I was hand coding binary all day.

JSR is better so use that. And you can install npm deps from esm.sh instead.

i use esm.sh and that’s how i noticed the outage.

cached packages resolved during the outage, but unpinned versions 404’d

my hot fix this morning was to pin my npm packages to cached versions on esm.sh

for deno packages, i tried to pin using the npm:* syntax, but those failed to resolve, so my hotfix was the same as above.

minor inefficiencies

Not surprising considering the JavaScript ecosystem....

... I am just joking. Please don't downvote me for it.