Stack trace from a coffees script application showing the original source code, annotated with code authors from Git.
Source maps support
Luckily, there is an established solution for dealing with this problem: source maps. Tools like Webpack and Gulp can produce a source map with the minified code. Using that source map, we can reconstruct the original code and show you an unminified version of the stack trace, automatically. Just make sure your asset pipeline outputs source maps, and deploy the source maps together with your other assets, then we’ll take it from there.
For more details on source maps, check our docs.
Normalizing stack traces
Browsers aren’t exactly known for their strict adherence to standards, which is also true for how they format stack traces. To make sure that the same errors from different browsers are grouped together, we invested a lot of time into normalizing stack traces across browsers.
By the way, you can learn more about this topic in Kenneth Auchenberg’s talk on how he built our client-side JS and AngularJS integrations