You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 14, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 14, 2026. It is now read-only.
[gulp] Starting 'less'...
[gulp] Plumber found unhandled error: [gulp] Error in plugin 'gulp-less': .make-
grid-columns is undefined in file bower_components\bootstrap\less\
grid.less line no. 48
[gulp] Finished 'less' after 314 ms
[gulp] Starting 'less'...
[gulp] 'less' errored after 317 ms .make-grid-columns is undefined in file bower_components\bootstrap\less\grid.less line no. 48
I also tried putting plumber inside the lazy pipe:
[gulp] Starting 'less'...
[gulp] 'less' errored after 317 ms .make-grid-columns is undefined in file bower_components\bootstrap\less\grid.less line no. 48
Lazystream uses stream-combiner inside, which returns one stream with one error handler for all underlying streams, so you get error object with information, from which stream it comes from:
[gulp] Using gulpfile /Users/floatdrop/gulp-lazypipe/gulpfile.js
[gulp] Starting 'default'...
{ plugin: 'gulp-less',
showStack: false,
name: 'Error',
message: 'Unrecognised input in file /Users/floatdrop/gulp-lazypipe/css/1.less line no. 12',
fileName: '/Users/floatdrop/gulp-lazypipe/css/1.less',
lineNumber: 12 }
Gulp-plumber will not add it own error handler, if there is one already defined.
Encountering this as well. Adding .on() to the lazypipe instance is not an option in my case (exporting lazypipes as a node_module). @floatdrop Would having an option to force plumber attaching it's own error handler (even if there is already one attached) fix this?
Activity
floatdrop commentedon Jun 12, 2014
Last code snippet is working fine for me, but with small addition:
Lazystream uses
stream-combinerinside, which returns one stream with one error handler for all underlying streams, so you get error object with information, from which stream it comes from:Gulp-plumber will not add it own error handler, if there is one already defined.
avanderhoorn commentedon Jun 29, 2014
Even though the reference has come through to this issue, I've also run into this issue with the following floatdrop/gulp-watch#52.
mgcrea commentedon Oct 10, 2014
Encountering this as well. Adding
.on()to the lazypipe instance is not an option in my case (exporting lazypipes as a node_module). @floatdrop Would having an option to force plumber attaching it's own error handler (even if there is already one attached) fix this?gligoran commentedon Sep 23, 2015
If anyone is still having problem with this, I found a work-around reading this article: http://lkrnac.net/blog/2014/10/watch-file-changes-propagate-errors-gulp. It provides this explanation:
So, to make plumber not crash, include it in all of your pipes. It's not pretty, as there's all of a sudden a lot plumbers everywhere, but it works.
@floatdrop: Are there any dangers of not calling
plumber.stop()?floatdrop commentedon Sep 23, 2015
@gligoran nope, it just restores original
.pipefunction, nothing else.