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
When something goes wrong, lessc writes to stdout, not to stderr
For a simple repro, you can just invoke lessc | wc -c. Should be zero, as the error message should be written to stderr.
(This issue originally included that lessc wasn't setting an erroneous exit code. It seems I was testing it wrong, and lessc does do the right thing there. Not sure what I did...)
Okay, edit 3: some errors don't correctly set an exit code. Here's one example:
When something goes wrong,
lessc
writes to stdout, not to stderrFor a simple repro, you can just invoke
lessc | wc -c
. Should be zero, as the error message should be written to stderr.(This issue originally included that
lessc
wasn't setting an erroneous exit code. It seems I was testing it wrong, andlessc
does do the right thing there. Not sure what I did...)Okay, edit 3: some errors don't correctly set an exit code. Here's one example:
But others do. An interesting roulette when using
lessc
from build scripts.The text was updated successfully, but these errors were encountered: