NPM: 429 Too Many Requests

#1

Post by kerpele » Mon, Feb 17, 2020, 12:45 PM UTC

NPM: 429 Too Many Requests
github.com

Re: NPM: 429 Too Many Requests

#2

Post by darekkay » Mon, Feb 17, 2020, 1:05 PM UTC

Check their status page [1] to see the progress:

> Investigating - We are currently investigating 403 / 429 errors received by some users.

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

Re: NPM: 429 Too Many Requests

#3

Post by dijit » Mon, Feb 17, 2020, 1:08 PM UTC

I was (incidentally) just looking for a way of running a npm repository. Apparently it is not so simple as running a web server with a manifest (which is the case for basically every other package manager out there). Is there a reason for that? Is npms approach somehow better?

The thing with using web technology for distribution is that it’s easily accessible and, crucially, that it’s cachable in-line.

Re: NPM: 429 Too Many Requests

#4

Post by cpclermont » Mon, Feb 17, 2020, 1:08 PM UTC

Some users in the issue are reporting it's fixed.

Re: NPM: 429 Too Many Requests

#5

Post by ORioN63 » Mon, Feb 17, 2020, 1:09 PM UTC

darekkay wrote: post #2

Check their status page [1] to see the progress: > Investigating - We are currently investigating 403 / 429 errors received by some users. [1] https://status.npmjs.org/

It seems the issue is resolved at the moment. From the same link

> Monitoring - Our content delivery partner has informed us they've implemented a fix. We are monitoring. Feb 17, 13:07 UTC

Edit: And in the OP GH thread, people are also mentioning it's back up.

Re: NPM: 429 Too Many Requests

#6

Post by gmemstr » Mon, Feb 17, 2020, 1:09 PM UTC

This seems to be slowly clearing up.

Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Re: NPM: 429 Too Many Requests

#7

Post by [deleted] » Mon, Feb 17, 2020, 1:10 PM UTC

[deleted]

Re: NPM: 429 Too Many Requests

#8

Post by Philomath » Mon, Feb 17, 2020, 1:11 PM UTC

If this is causing production CI/CD pipelines to fail, this might be a bigger issue than it seems. Has this already happened in the past with npm?

Re: NPM: 429 Too Many Requests

#9

Post by warpech » Mon, Feb 17, 2020, 1:12 PM UTC

If this happens in future, you can switch an NPM mirror, such as:

- https://open-registry.dev/#get-started

- https://npm.taobao.org/

WARNING: Research who runs the mirror before putting your trust in it.

How to turn on:

  npm config set registry https://npm.open-registry.dev

How to turn off:

  npm config delete registry

Re: NPM: 429 Too Many Requests

#10

Post by lm28469 » Mon, Feb 17, 2020, 1:14 PM UTC

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)