5 ms·
... until LeftPad 2.0 [1] happens, then everyone will be mocking those who didn't commit node_modules. 1. http://blog.npmjs.org/post/141577284765/kik-left-pad-
by linkregister 9y ago
... until LeftPad 2.0 [1] happens, then everyone will be mocking those who didn't commit node_modules.
1. http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm
- granos 9y agoSeriously. I've been on a deployment that failed because China blocked access to Github for a little while over some piece of code in some repository. Make sure your dependencies are available.
- keiyakins 9y agoWhat's wrong is that the package manager and repo manager aren't talking to one another. "Keeping a copy of the dependency with your code" and "copy and pasting the code" should not be the same thing.
- linkregister 9y agoI 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.