From Node Weekly #326[1]:<p>The Main npm Repository Suffered an Outage on Monday[2] – But Here's What to Do For Next Time.. — For a period of time on Monday, the main npm repository was returning 429 “Too Many Requests” responses, breaking some people’s installations and CI processes (here’s a postmortem of why[3] – it was due to a Cloudflare policy change and not npm's fault).<p>This sort of thing happens from time to time, but is a good reminder to be aware of being able to switch to alternative mirrors[4] or begin caching and proxying the fetching of dependencies via a tool like Verdaccio[5]. More ideas in this Twitter thread[6].<p>[1] <a href="https://nodeweekly.com/issues/326" rel="nofollow">https://nodeweekly.com/issues/326</a><p>[2] <a href="https://github.com/npm/cli/issues/836" rel="nofollow">https://github.com/npm/cli/issues/836</a><p>[3] <a href="https://github.com/npm/cli/issues/836#issuecomment-587019096" rel="nofollow">https://github.com/npm/cli/issues/836#issuecomment-587019096</a><p>[4] <a href="https://open-registry.dev/" rel="nofollow">https://open-registry.dev/</a><p>[5] <a href="https://verdaccio.org/en/" rel="nofollow">https://verdaccio.org/en/</a><p>[6] <a href="https://twitter.com/bitandbang/status/1229467759437910016" rel="nofollow">https://twitter.com/bitandbang/status/1229467759437910016</a>