Yes of course!
Because we gain a lot of benefits while bundle/package our libraries/packages and stuff.
npm doesn't install peer dependencies anymore
the left-pad gate taught us to not rely on npm i on a project initialisation.
Developers coming from user languages with different packages managers complain about how much HDD space npm consumes. Having a 3TB HDD in a $500 machine and yet still complain about 100mb projects ;-) We can make them shut by using browserify/webpack/rollup and publish our single binary to npm with the minimal size possible. No additional packages required downloading.
Downloading a single binary from npm is faster than downloading many dependencies and compile or link binaries to node_modules/.bin folder
Executing a single binary is faster than dynamically follow a bunch of import commands
And of course, our binary is heavily optimized too - dead code elimination, inlining code, minified variable, function and class names, etc.
Denny Trebbin
Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.
Yes of course! Because we gain a lot of benefits while bundle/package our libraries/packages and stuff.
npmdoesn't install peer dependencies anymoreleft-padgate taught us to not rely onnpm ion a project initialisation.npmconsumes. Having a 3TB HDD in a $500 machine and yet still complain about 100mb projects ;-) We can make them shut by usingbrowserify/webpack/rollupand publish our single binary tonpmwith the minimal size possible. No additional packages required downloading.npmis faster than downloading many dependencies and compile or link binaries tonode_modules/.binfolderimportcommands