Gulp.js: The streaming build system

Re:Gulp.js: The streaming build system by aymericbeaumet on Thursday August 21, 2014 @12:12PM (#8208071)

Even though they are clearly related, Gulp and Grunt are fulfilling different purposes. You should carefully examined your needs before choosing one over another.

I recently switched to Gulp for several projects, and I'm thinking of switching back to Grunt.

Gulp lacks of some important features. For instance, it does not allow to sequentially execute tasks: everything is done in parallel. This could for sure be emulated by using async, but the overhead is not worth it.

On the other side, Grunt does support sequential and parallel tasks execution, but is more verbose and does a lot of file writing on the disk (though it is relatively moderate).

One concrete example for sequential tasks execution (easily done with Grunt):

- Watch JavaScript files, when a modifications is detected:

  - lint files -> [JSHint, JSCS]

  - if success: launch tests -> [Karma, Mocha]

  - if success: notify

- If any failure occurs: notify and abort the sequence

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by adamors on Thursday August 21, 2014 @01:09PM (#8208399)

> it does not allow to sequentially execute tasks: everything is done in parallel

There's a package[1] for Gulp which does exactly that.

[1]: https://www.npmjs.org/package/run-sequence

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by aymericbeaumet on Thursday August 21, 2014 @04:40PM (#8209465)

I didn't know about it! Thanks

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by terinjokes on Thursday August 21, 2014 @01:05PM (#8208364)

We're adding the ability to handle sequential tasks (and other cool combinations) in Gulp 4. See bach[1] for some ideas.

[1]: https://github.com/phated/bach

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by aymericbeaumet on Thursday August 21, 2014 @04:51PM (#8209519)

I remember some discussions on Gulp's issues tracker where maintainers were reticent about integrating sequential tasks execution.

But that's great if you are going to do it. This may make me come around and give a second chance to Gulp.

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by vlunkr on Thursday August 21, 2014 @01:14PM (#8208420)

There are ways, like others have said. There is also a callback system you can use to make things sequential, but last time I looked it wasn't well documented

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by aymericbeaumet on Thursday August 21, 2014 @05:14PM (#8209649)

There are always ways. But I find Grunt much more handy to do it.

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by Recoil42 on Thursday August 21, 2014 @01:05PM (#8208367)

"For instance, it does not allow to sequentially execute tasks: everything is done in parallel."

This is false. You can set perquisites for a task, which will be executed in sequence.

[ Parent | on HN ]

Re:Gulp.js: The streaming build system by aymericbeaumet on Thursday August 21, 2014 @05:08PM (#8209620)

I think you are talking about this[1], indeed you are right.

However, task dependencies allows sequential tasks execution, but that's not very handy as you may want a same task to be executed in two different sequences.

Let's see a simple example on which I honestly struggle to reproduce with Gulp:

  [Lint, Test] -> Concatenation -> Minification

  Watch -> [Lint, Test] -> LiveReload

How would you do such a setup without having a redundancy in your tasks declaration?

[1]: https://github.com/gulpjs/gulp/blob/master/docs/recipes/runn...

[ Parent | on HN ]