Ability to specify `stack: true` when calling `captureMessage`

[benvinegar]

Basically, when doing captureMessage, you might want to also see a trace up until that point.

We're considering making this the default, but there could be performance implications if every logging message included a trace.

[vincentwoo]

Seconding this. Also, right now Sentry doesn't capture the filename of the source file originating the log message, which makes it impossible to see which asset version produced the event.

[benvinegar]

@vincentwoo – the tricky thing about that, is that we'd need to try/catch inside captureMessage, at which point the file might be raven.js or vendor.js or some file from which the message didn't actually originate.

We'd have to throw an error, catch it, and traverse up the stack trace and try to estimate at which frame the message originated from (discounting Raven frames). This can be tricky because of minified code.