3 ms·
I'm glad for the relatively low amount of breaking changes this time. npm prepare should be a nice addition (using prepublish for, e.g., installing typings is s
by Lx1oG-AWb6h_ZG0 10y ago
I'm glad for the relatively low amount of breaking changes this time. npm prepare should be a nice addition (using prepublish for, e.g., installing typings is such a non obvious hack).
That said, I'm still not certain about shrinkwrap excluding dev deps. I mainly use it to ensure my build agent uses the same dependencies as my dev box, and at a time when things like babel pull in a ridiculous amount of sub dependencies, it really does not make sense to not lock down _all_ your dependencies by default.
- madeofpalk 10y agoThe difference between regular dependencies and devDependencies is very blurry with things like Webpack and Babel - they're not required at runtime but they're responsible for significant amounts of runtime. Luckily, npm shrinkwrap accepts a --dev option to include devDependencies
- bsimpson 10y agoAsk yourself "will authors consuming my module need this dependency?". If not, it's a development dependency. If you're including pure-JavaScript artifacts in your npm releases, downstream authors probably don't care about your Babel/Webpack configuration.