NPM website was down
status.npmjs.org
status.npmjs.org
[0] https://arstechnica.com/information-technology/2026/01/odd-a...
It's not DNS
There's no way it's DNS
It was DNS
If it's not DNS it's MTU if you're a person and BGP if you're a company.
Ironically, both Nandu and Verdaccio are implemented in Tyepscript and install via npm.
(Same logic obviously applies to Python packages, Docker images, etc.)
Both yarn and pnpm support http/2 which speeds up the bazillion requests quite a bit.
I took that for granted back then and just assumed it was standard enterprise policy
Deno already does this invisibly by default.
All packages are stored in the global cache.
No need to store multiple versions of the same dependencies across projects.
To the code in your projects: there is no such thing as a global cache. Just import your dependencies like normal and deno maps them to the global cache.
They seem to be doing a pretty good job at wrecking both GitHub and npm at the same time.
Keep up the good work Microsoft.
Let's shoot for 100% downtime though. Thanks.
* You can actually have an organisational structure (folders/namespaces), and projects can be moved around with automatic redirects. Also, inheritance of access controls, variables between the namespaces
* GitLabCI is organised in a way that makes supply chain attacks less of a risk. GitHub Actions takes the NPM/JS approach, where every step is an action, one you usually need to get off someone, with shoddy versioning, tons of transient dependencies, etc. In GitLabCI you can have templates, but you don't have to use an external template for every bit. It's shell scripting on top of containers, so you can have custom container images with your stuff, or custom scripts, or templates that bundle it all.
so, while you’re technically right, these features are apparently paywalled heavily on github.
ime you get more features on gitlab for the same price (or less). i switched fully two years ago and im not going back.
SSO, access tokens, secrets are all bound to the Organization level - if you work on multiple Organizations you have to log in separately... You also cannot have nested Organizations.
Its a problem they know about, but have no plan to fix before 2027.
Thus, we're moving off GitLab.
The "surprise, you can't review all the files in your PR" using GitLabs standard web based tooling makes it a no-go.
With GitLab, when you hit the rate limit, any file "past" that limit doesn't even show that it exists in the MR. It just looks like the MR is missing a bunch of stuff, with no workaround available. :( :( :(
:)