I agree, ideally artifacts should be stored and cached, e.g. in a stored container or as a tarball. Other than a local npm mirror, what do you think is the bes

I agree, ideally artifacts should be stored and cached, e.g. in a stored container or as a tarball. Other than a local npm mirror, what do you think is the best way to store artifacts for new builds? Vendoring code is not a bad solution if it permits new builds to occur even in the event of a package manager outage. I see vendoring code as the simplest solution for small companies who don't want the management overhead of running a local mirror of package managers. That said, I'm very much open to learning a new technique for handling this problem.