Matt Edelman

As to the question of being over-engineered... ┐(ツ)┌ ... that's a pretty subjective question we shouldn't, and won't, attempt to "resolve" To attempt to get at an actual issue here,...

@bryanspears what about an additional debug log message here, to print out any errors: https://github.com/krakenjs/kraken-devtools/blob/master/lib/middleware.js#L83 ``` if (!!err) { debuglog('Encountered error: ', err); } ``` For less, you would get...

A wise teammate of mine pointed out that the 500 middleware does intercept this error. You can currently see the error by setting `NODE_DEBUG=kraken/middleware/500`

Initially I'd tried to see all the logging of all kraken\* modules by using `NODE_DEBUG=kraken*` Didn't seem to work but I haven't yet read the debuglog doc.

Or I guess override it in your development.json

I think it would be nice if all the logging could be turned on easily. Apparently debuglog doesn't work the way I thought it should. I've been using https://github.com/visionmedia/debug in...

Passing through again, trying to resolve issues of old. @bryanspears and others.. Do you think the error should be thrown in the less plugin itself?

Pardon that... Let's not say we are throwing any errors. But based on Bryan's earlier comment about a "top-level option to see all the errors" I would propose that we...

It would essentially be a one line change to add `console.error` here: https://github.com/krakenjs/kraken-devtools/blob/master/index.js#L50 To add a conditional around that and make it configurable would be a 3 line change... Or...

Agree. We should work on a gulp variant. I just now heard of broccoli. So many build thingies out there. PRs welcome of course!