Emit correct exit code on Sass compilation errors if env != development

[polarbirke]

Use hard exit for prod, staging and testing environments (this
is especially important for CI debugging) when Sass encounters
compilation errors. On the other hand, it is useful to only emit
"soft" errors during local development; it would be frustrating
if watch/serve process would crash every time a Sass compilation
is not successful (e.g. because of a typo).

[sebastiankugler]

Failing hard in environments other than development is definitely an improvement compared to failing soft everywhere.

However, I'm wondering if there is a better way to allow soft errors for background tasks (watch/serve) while keeping the hard errors for build tasks? I don't use watch/serve regularly and I would appreciate it if a build process (phlough install) would fail with a hard error if there's a problem in the gulp compile (otherwise you would get a success message for the install which I would consider misleading).

Can you see in gulp whether it's running in a watch/serve process? Could you start the watch/serve with a parameter to suppress hard errors?

[polarbirke]

Super Idee @sebastiankugler 👍