Whether in the error log on the server side or forwarded to the client and console.logged, I just want to see what happened instead of having to dig. Currently, the module will error out saying "Failed dependencies", so I check for circular module dependencies and find none...then I try commenting out the style definitions and it works fine.
Version: 1.23.0
Severity: normal
Is this against current master? With gerrit 109956 there can be "useful stacktraces when there are issues with style file like LESS compilation errors"
I'm running current master and am, I think, seeing issues with LESS but no logging on the server or client side.
I can try to confirm somehow, if you'd like.
Server-side the unit tests now validate Less syntax.
Client-side the exceptions are printed in a comment in the load.php response. This is somewhat invisible if you're not looking for it, which is why T110659 exposes them to the browser console.
I'm closing it since the above should satisfy the underlying use case for this task.