Hacker News new | ask | show | jobs
by nallerooth 3659 days ago
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.
1 comments

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?