@contra One possible solution is to just use new the newly defined trigger(from issue #32, I was thinking of that all along) whenever a watch is used, so like your example in that issue:

gulp.task 'default', ->
  gulp.watch("./client/js/**")
    .pipe(gulp.trigger 'js')
    .pipe(gulp.trigger 'coffee')

This does require having to change how tasks work, so that they'd function more like event stream maps than anything.

Another possible solution is adding some stuff to gulp-util that allows you to make 'file blobs', or collections of files that check which files are recomputed, and always send the full file list down the pipe. You could create a file blob from gulp-util that would read the incoming stream and automatically add new files. Any change in the files list, and the whole file list is sent down again. This would also make passing things along easier.

Example for gulp-concat:

var es = require('event-stream'),
  path = require('path'),
  util = require('gulp-util');

module.exports = function(fileName){
  if (!fileName) throw new Error("Missing fileName option for gulp-concat");

  var blob = new util.FileBlob(); // Create a file blob

  function concatFiles(files, cb){ // files is an array that blob stores

    var joinedContents = files.map(function(file){
      return file.contents;
    }).join('');

    var joinedPath = path.join(path.dirname(files[0].path), fileName);

    var joinedFile = {
      shortened: fileName,
      path: joinedPath,
      contents: joinedContents
    };

    cb(null, joinedFile);
  }

  return es.pipeline(
    blob.add, // blob.add adds a file to the blob
    es.map(concatFiles) // our concat function
  ); 
};

The resulting code is shorter and arguably more concise. Anyway, this is a pretty big change. I think I may have to pull this into its own issue.

Uh oh!

gulp.src(..).pipe(gulp.watch(..)) #13

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

`gulp.src(..).pipe(gulp.watch(..))` #13