[pauldotknopf]

There is a large amount of stuff to know before you can develop and debug the piping stuff in gulp, I grant you that.

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?

[nallerooth]

As he states in the article: sometimes gulp plugins are not updated to support new versions of libraries, resulting in developers being stuck on old versions of tools. There's also a risk that the plugin contains bugs, in which case you can either fix them yourself or wait for the plugin maintainer(s) to do it. Both of those alternatives takes time, energy and focus from your main project, which makes it a good thing to avoid if possible.

[pauldotknopf]

But my point is that you can use gulp only (no plugins), and throw your npm scripts into gulp tasks.

Where is the risk there?