Allow hooking events and contexts about gulp HOT 7 CLOSED

Can you provide a clearer example? Not sure what you're asking

from gulp.

I want to fork on a event and process files within that fork thus for the above, given:

src/{a,b}/{foo,bar}.coffee

would produce:

src/{a,b}.js

from gulp.

Why not just use two streams? I'm not sure I see the use case or that it's common enough to add what seems like a hefty feature

from gulp.

can you show me an example? do you mean two tasks? because I would need a task per directory and per every other directory with a *.coffee file within it which would quickly become painful

from gulp.

For the example in your last post:

gulp.task('coffee', function() {
  var dirs = ['a','b'];
  dirs.forEach(function(d){
    gulp.src('./src/'+d+'/**.coffee')
       .pipe(coffee())
       .pipe(jshint())
       .pipe(concat(d+'.js'))
       .pipe(gulp.dest('./static'));
  });
});

from gulp.

the coffee files would be spread over many dir's but I guess I could read the dirs at runtime, I never thought of that, thanks.

from gulp.

Gulp tries to find a good point between sugar and simplicity. Features like this we will usually do it as code and not include it in the core library. If you find yourself doing something tedious over and over feel free to write a userland module that simplifies it and tag it as a gulp plugin!

from gulp.