NPM: 429 Too Many Requests

Re:NPM: 429 Too Many Requests by sethammons on Monday February 17, 2020 @08:21AM (#22347461)

This is one of the reasons why, in Go, my team vendors our dependencies. For any service that seeks stability and the ability to deploy any time, removing networked build dependencies is important.

[ Parent | on HN ]

Re:NPM: 429 Too Many Requests by ratata on Monday February 17, 2020 @08:33AM (#22347536)

> vendors our dependencies

Is that like a local cache?

[ Parent | on HN ]

Re:NPM: 429 Too Many Requests by sethammons on Monday February 17, 2020 @08:40AM (#22347593)

Vendoring is checking in your dependencies with the source. You can def consider that a local cache. The next step up is to run your own proxy server (pretty much a package server / mirror). Next is to use a service like artifacory that does similar.

[ Parent | on HN ]

Re:NPM: 429 Too Many Requests by erik_seaberg on Monday February 17, 2020 @04:46PM (#22351125)

We should call it a backup. Calling it a cache puts people in mind of size/hit ratio tradeoffs; what's needed is zero tolerance for loss of mission critical code.

[ Parent | on HN ]