Handling compile errors so it doesnt halt gulp watch tasks

[afreidz]

When running gulp-handlebars in conjunction with gulp watch, errors are "thrown". This causes the gulp watch task to halt. Here the error message is logged to the console and the compiled template outputs an error message.

[lazd]

This is how errors are handled in gulp. If you don't want watch to stop, add a listener to the error event. See this gulp issue for details and this docs page for a more complex use case.

This needs to be documented better in gulp itself.

[afreidz]

Yes, while the error listener does not HALT gulp, it also never completes the compile. Therefore when you fix the error, the task never gets re-run. Not sure if that's as designed or not. I use a similar pattern, that you suggested, on error for another gulp module (gulp-less) and that task will log the error, but finish the task. Any insight on how this can be handled?

[lazd]

Please read the issue I linked, it covers the exact problem you're mentioning. This may still be a problem with the plugin, but I'm not sure. Feel free to dig into gulp-less's internals and report back on how it handles things differently.

[mietek]

The problem was actually fixed in d4aad97. Among other fixes, the key fix was emitting errors properly:

     if (file.isStream()) {
-      return this.emit('error', new gutil.PluginError('gulp-handlebars', 'Streaming not supported'));
+      this.emit('error', new gutil.PluginError(PLUGIN_NAME, 'Streaming not supported'));
+      return callback();
     }

[lazd]

@mietek, thanks for following up on this. It sounds like gulp-handlebars is behaving as it should.