Improving JavaScript Reports

[dcramer]

As part of some recent changes to Sentry we should explore how we could greatly customize/improve JS reports. This is the master ticket for tracking and discussing potential changes to JS reports.

Some initial thoughts:

• Offer two stack views (sourcemaps, no sourcemaps)
• Implement breadcrumbs
  • This is useful beyond JS, but we can start there
  • trackjs implements a bit of this, and we know understanding user inputs is valuable, but take it all with a grain of salt
• Clearly call out use of sourcemaps to know URL, name, basic properties (possibly as a meta object?)
• Support webpack dep versions [package.json](how hard is this?)

[benvinegar]

• Use sourcemaps to translate back minified variable/method names that appear in error messages back to their original form
  • e.g. "c is undefined" => "doThing is undefined"

[benvinegar]

Offer two stack views (sourcemaps, no sourcemaps)

✅ – We let you toggle between them.

Implement breadcrumbs

✅ – Done!

Clearly call out use of sourcemaps to know URL, name, basic properties (possibly as a meta object?)

✅ – We show you the URL of the source map that was applied.

Support webpack dep versions [package.json](how hard is this?)

❌– Not sure what this means. We show you the version of libraries in the stack trace or something?

Use sourcemaps to translate back minified variable/method names that appear in error messages back to their original form

❌ – We tried. It's super hard.

Gonna close this though. We hit most of the notes.