“gulp-notify: [Error running Gulp] Error: write after end”
Closed this issue · 2 comments
I get this message on Windows 8 (not tried on any other OS) when saving a JavaScript-file. gulp-notify
still runs after the message, but stops triggering on subsequent saves.
I only get this error on the JavaScript section of the gulp setup for the project that I work on – it doesn’t fail when saving LESS-files.
It seems as if something is written to the stream after the stream is closed (gulp-notify returns a stream per default). I think this might be related to the v1.8.0 release, where the stream is closed straight away. What version of gulp-notify
are you running?
Try doing
➜ npm ls gulp-notify
from you're project root (where gulpfile.js is located)
Issue solved through chat. Problem was usage, and gulp-notify
logging an error of faulty usage.