feature/question: Console breadcrumbs line numbers suggestion

I’m complaining about the raven.js with no line numbers associated to all console.log() calls. #723 #48

These were closed as “wont fix”, the workaround given was to disable the breadcrumbs feature.

I want the breadcrumbs feature, but also to be able to see the line number which generated the console.log() call…

Why can’t you just concatenate or prefix a string to the console.log() payload containing this information?

The breadcrumbs payload sent also doesn’t contain line numbers so its kind of useless… Here’s a screenshot of what got sent to sentry. The console.log() message was sent, but with no line numbers.

My suggestion is to add line numbers to what I see in the console, and in what gets sent to sentry. If this is a “wont fix” can you please explain why? Not having line numbers makes debugging pretty difficult. The whole point of using a library like this is to help make debugging easier.

Specifically why not just append to the .message property of that json object, a string like " - Happened on Line 111 in File xyz.js". Devtools does this out of the box & this library not only doesnt do it, but also breaks the usefulness of devtools.

[billyvg]

@joshribakoff I’m not sure if you can do this in other browsers, but you can blackbox @sentry (or raven-js for older SDKs) in chrome devtools:

[DerekJDev]

If anyone is using Microsoft Edge and runs into this, you need to go into DevTools --> Settings --> Library Code. Then add /@sentry/ as a library code pattern. In the dropdown, make sure the value is “Library code”, not “Disabled”.