Join us for a live demo on Wed. Dec. 11: Debugging Salesforce Apex Applications with Error Monitoring. Register Today!
April 20th, 2017 • By Jesse Gibbs
Due to the need for source maps, debugging minified code will always be inherently problematic, but we’ve just introduced several improvements to Rollbar’s source map handling that will make troubleshooting much, much easier.
When a Rollbar stack trace includes a minified file that doesn’t have a matching source map, you’ll now see an information message that links you to your project’s source map screen where you can further troubleshoot why the source map wasn’t available.
More often than not, you look at your source maps because something didn’t work as expected. You can now see when Rollbar fails to access a source map, including detailed information about what happened.
On large projects with frequent deployments, you may have a lot of source maps generated from a lot of different code versions. With our new search capability, you can find source maps based on code version or filename.
Finally, we’ve fixed a bug that many of you told us about - When deleting a source map, you will remain on the same page you were previously viewing. This makes it much easier to clean out old source maps that are no longer needed in your project.