Why I Left Gulp and Grunt for Npm Scripts
medium.freecodecamp.com
medium.freecodecamp.com
- Write your build with the full power of the language you use everyday and orchestrate it with a thin layer like Gulp - Write uncommented (and uncomment-able) bash scripts where parallelism, streaming, and cross-platform compatibility require nontrivial effort
Gulp isn't as complicated as some have insinuated. You don't even need to use Gulp plugins if that's a concern–it's just Node!
I'd much rather write Javascript to build Javascript than memorize CLI arguments and break all of my scripts on Windows.
I will say that the best part of npm scripts is that they're not Grunt :)
But, what are you going to wind up using in npm scripts for your resource compiling? Webpack? Browserify?
Why not put that all into a gulp file? Gulp files are great for non-piping-streaming tasks. It has great support for chaining tasks and making tasks dependent upon others.
What benefit do I get by actually moving to npm scripts, that I couldn't have in a gulp file?
Where is the risk there?