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.
I'm having a similar problem using gulp-postcss, gulp-plumber, and gulp-watch together — task shown below. When the task encounters a CSS error, the task remains open and the error is logged per the warn error handler passed in, so all is good so far. But the build files aren't updated with any changes made to the source files, like fixing the error.
gulp-watch does still continue to log that changes were detected in the source files; they just don't get processed anymore unless I restart the task over again.
Bad fix:
Will work with gulp-notifyhttps://www.npmjs.com/package/gulp-notify import notify from 'gulp-notify'; and
Instead .pipe(plumber()) insert .pipe(plumber({ errorHandler: notify.onError('Error: <%= error.message %>') }))
I don't know why it works, I found it when I wanted to delete gulp-notify, he has his own problems (with notifications).
Activity
msfragala commentedon Nov 8, 2015
I'm having a similar problem using
gulp-postcss,gulp-plumber, andgulp-watchtogether — task shown below. When the task encounters a CSS error, the task remains open and the error is logged per thewarnerror handler passed in, so all is good so far. But the build files aren't updated with any changes made to the source files, like fixing the error.gulp-watchdoes still continue to log that changes were detected in the source files; they just don't get processed anymore unless I restart the task over again.ambethia commentedon Feb 19, 2016
Has anyone found a solution/workaround for this yet?
mgol commentedon Mar 3, 2016
Might be related: #30 (comment)
armandabric commentedon Jan 11, 2017
I have the same issue.
marko-g-stojkovic commentedon Nov 22, 2017
I have this problem, but nobody resolved it as I see...
alkorlos commentedon Jan 31, 2021
Bad fix:
Will work with
gulp-notifyhttps://www.npmjs.com/package/gulp-notifyimport notify from 'gulp-notify';andInstead
.pipe(plumber())insert.pipe(plumber({ errorHandler: notify.onError('Error: <%= error.message %>') }))I don't know why it works, I found it when I wanted to delete
gulp-notify, he has his own problems (with notifications).rollecode commentedon May 24, 2021
Just notice the same. Solutions?