When you trigger an error in the sass task the watcher gets stuck.

[gijsroge]

If you have an error you in your sass files the build throws an error but does not recompile after you fix the issue.

This forces you too re trigger the watch task each time you make a mistake.

Not sure whats causing this.

[MartijnCuppens]

Hmm, I can't reproduce that. Could you scope where things go wrong?

[gijsroge]

@MartijnCuppens yeah I was planning on debugging it. Just created an issue so I can keep track of the progress.

[gijsroge]

I've setup a repo where you can reproduce the issues.

Just run the buildozer watch command and uncomment https://github.com/gijsroge/plumber-sass-watch-issue/blob/master/scss/subfolder/_test.scss#L3

It only happens if you import a file from a subfolder that triggers an error .. 🤷‍♂️

Found a couple of related issues.
floatdrop/gulp-plumber#34
floatdrop/gulp-plumber#30
floatdrop/gulp-plumber#42

The quick fix is to implement a custom errorHandler that emits an 'end' event.
floatdrop/gulp-plumber#30 (comment)

Looks like we have 2 options available.
Either we apply the quick fix
Or we could look into handling errors by ourself (https://gulpjs.com/docs/en/getting-started/async-completion#using-an-error-first-callback)

Whats your opinion?

[MartijnCuppens]

Maybe #22 causes this. I think we better figure out how to fix that issue first, solving that might solve this (not sure at all, but I know for sure are callbacks are currently not ok)

[MartijnCuppens]

This was actually solved by asyncing the cssCompile() function in #32 🎉

buildozer/lib/gulp/css.js

Line 35 in a285c28

async function cssCompile({src, dest, browserSync = false}) {

[gijsroge]

🎉 🎉