Improved Source Maps for frontend errors

We’ve made some changes to our source mapping for frontend JavaScript errors. Previously, we detected whether or not your JavaScript files have source maps in the browser, but this turned out to be unreliable in some cases.

That’s why we decided to move source map discovery into Opbeat itself. This means it should be much more robust going forward.

Before

Before

After

After

As you can see, we’ve also improved how we display the location of the error in the header of the error group, using information from source mapping.

The goal of this change is to make sure cache busting techniques like adding hash sums to file names doesn’t break error grouping.

This update is already live for you in the source map of your frontend errors, and doesn’t require any changes in your setup.

If you haven’t set up source maps yet, learn more in our docs article.

If you have any questions or feedback, let us know in support@opbeat.com.

About the author
Casper Hübertz is a designer and air drummer.
You can follow him on Twitter or on Dribbble.