barc / express-error Goto Github PK

Hey @mgutz, love the library! We're looking to use it Box, but have run into this problem when testing.

Currently, express-error will output to the console an incredibly long stack trace and lines of text from each stack frame (if contextLinesCount is set), usually resulting in hundreds of lines for a single error.

While all this information is easy to read when formatted as HTML + CSS, it's impossible to read from the console. The most important information is at the top, so you have to scroll hundreds of lines up just to find and read the error message. If two errors have occurred, this becomes nearly impossible to parse.

I'm about to push a PR with a fix, but I'd love to get your thoughts.

Hey,

I've launched the example app, as described in the docs, but I can't seem to get the source code display/highlighting to work under Windows (it seems to be working under Ubuntu).

Is this a known issue?

TypeError: first argument must be a string or Buffer
    at ServerResponse.OutgoingMessage.write (http.js:715:11)
    at ServerResponse.OutgoingMessage.end (http.js:804:16)
    at Object.exports.express3 [as handle] (..../node_modules/express-error/lib/expressError.js:244:18)
    at next (..../node_modules/express/node_modules/connect/lib/proto.js:194:17)

it's in

    return res.end(stack);

https://github.com/barc/express-error/blob/master/lib/expressError.js#L276
Need facility to configure it.

CoffeeScript supports source maps for a while now. Would be nice to show coffee source instead of compiled Javascript if map file exists.