TypeError: Object #<Object> has no method 'apply' about gulp-sequence HOT 7 CLOSED

fileChanged task has a mistake, you should use callback:

gulp.task("fileChanged", function(callback)
{
    // Try to access a non-existent object "event"
    webpack.watch(event.path, webpackOptions,
    {
        base: path.resolve(event.path)
    }, function(err, stats)
    {
        // ...
        callback(err)
    });
}

from gulp-sequence.

@zensh I understand that the task has a mistake (I acknowledged as much above). My point is that buggy user code should not cause the gulp-sequence plugin to crash. It should catch and recover from this kind of exception (print an error message and shut down gracefully).

from gulp-sequence.

I will improve it, and update for gulp v4

from gulp-sequence.

Hi, @cowwoc, watch task should write in this way:

gulp.task("watch", ["browser-sync"], function()
{
    gulp.watch(buildConfig.srcDir + "**/*.js", ["javascript"]).on("change", function() {
      sequence("fileChanged")();
    });
    gulp.watch(buildConfig.srcDir + "**/*.scss").on("change", function() {
      sequence("fileChanged", "css")();
    });
});

sequence return a thunk function that expect a callback as argument, change event listener called it with event object~, Object #<Object> has no method 'apply'.

from gulp-sequence.

Got it. Were any commits applied against improving error handling? I ask because I don't see any references attached to this issue.

from gulp-sequence.

[email protected], will throw a TypeError

from gulp-sequence.

Sounds good. Feel free to close this issue.

from gulp-sequence.