2 ms·
In NPM registry, yes. But in Node.JS ecosystem, it was left-pad's scope combined with inability of the community to adopt seasoned sysadmins' tools, like custom
by dozzie 10y ago
In NPM registry, yes. But in Node.JS ecosystem, it was left-pad's scope
combined with inability of the community to adopt seasoned sysadmins' tools,
like custom repositories to build artifacts without ever needing to touch
network (which is somewhat difficult to execute when you have dozens to
hundreds of dependencies for a trivial project).
- insin 10y agoI don't think the number of dependencies per individual project is a critical factor when setting up an internal npm mirror for all your projects (e.g. with Nexus [1] where I work) or vendoring dependencies per project (e.g. `npm shrinkwrap --dev && shrinkpack` [2]) - you're either doing it or you aren't. [1] http://books.sonatype.com/nexus-book/reference/npm.html http://books.sonatype.com/nexus-book/reference/npm.html [2] https://github.com/JamieMason/shrinkpack https://github.com/JamieMason/shrinkpack