I'm still having trouble catching Sass errors. Once I updated Gulp to 3.5, it doesn't seem like the errors ever get caught. Any help with that?

So, using the PHPUnit test, do you receive an feedback when there are errors. It no longer "kills" the process, but it still emits the same error I have been trying to resolve (this error is only thrown when a test fails, passing tests work fine as they did before)

events.js:72
throw er; // Unhandled 'error' event
^
Error: Command failed:
at ChildProcess.exithandler (child_process.js:637:15)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Process.ChildProcess._handle.onexit (child_process.js:802:5)
mikee at Traveller in ~/Documents/Projects/smith-guide on master*
$

Works perfectly for me. Are you using all the modules listed above?

Are you using the Gulp exec plugin? Above, I'm just doing:

var exec = require('child_process').exec;
var sys = require('sys');

Looking at the coffee module docs I see .pipe(coffee({bare: true}).on('error', gutil.log)). It looks like the on('error') has to be attached to the module function. I am not familiar with gulp or the sass module but would the following work?

gulp.task('css', function () {
    return gulp.src(sassDir + '/main.sass')
        .pipe(sass({ style: 'compressed' }).on('error', gutil.log))
        .pipe(autoprefix('last 10 version'))
        .pipe(gulp.dest(targetCSSDir))
        .pipe(notify('CSS minified'));
});

gulp.task('js', function () {
    return gulp.src(coffeeDir + '/**/*.coffee')
        .pipe(coffee().on('error', gutil.log))
        .pipe(gulp.dest(targetJSDir));
});

That used to work (with Gulp 3.4), but it doesn't seem to anymore. Even with it included, a parse error kills the watcher.

Secondly, on the exec problem. It may be due to not catching the errors. See here: https://github.com/robrich/gulp-exec/blob/master/index.js#L24-L33

Edit: hmm was worth a shot. Sounds like a potential problem upstream. I am hoping to switch to gulp soon but unfortunately stuck with grunt at the moment.

Hmm, I was thinking of trying a watch task that would do a composer dump-autoload if new directories were added.
Has anyone done anything similiar?

zanmoskotevc - You should be able to do that the same way this script is running phpunit. You can use child_process.exec to run composer dump-autoload.

@zanmoskotevc

You can do this as follows using the gulp-exec plugin:

gulp.task('composer-autoload', function() {
var options = {silent: false};
gulp.src('./app/acme/*/.php').pipe(exec('composer dumpautoload',options));
});

gulp.watch('./app/acme/*/.php', function(event){
gulp.run('composer-autoload');
});

Though using gulp.run has been deprecated, as of v3.5.

@mikeerickson that's similiar to what I have, thanks! :)

FYI, I have written a gulp-phpunit plugin and it should be available in nom in the next day or so. This version makes it plain simple to call :-)

param1 = path to php binary
param2 = options (currently only contains debug flag, will be expanded in future) [optional]

gulp.task('phpunit', function() {
var options = {debug: false};
gulp.src('./app/tests/*.php').pipe(unit('./vendor/bin/phpunit',options));
});

@jeffrey My plugin does not use gulp.run so works with all versions of gulp (including current 3.5)

@zanmoskotevc Have a look at the gulp-phpunit plugin which should be active tomorrow.

The gulp-phpunit plugin is now available on nom

https://npmjs.org/package/gulp-phpunit

npm install --save-dev gulp-phpunit

@JeffreyWay Use gulp-plumber to catch those errors.