Artifact Bundles: A simpler approach to un-minifying source maps

[mitsuhiko]

Anyone who has been tasked with configuring their application to upload source maps for Sentry issues knows how painful it can be. Heck, even if you successfully upload minified sources and their respective source maps to Sentry, mismatched abs_path or dist values can still prevent Sentry from un-minifying stack frames.

Our bundler plugins do alleviate some of these pains by automatically creating releases and uploading source maps on build. However, this is still built on the principle that a user must create a new Sentry release each time their application codebase changes.

As of today, we're announcing “Artifact Bundles”, a new way of un-minifying stack frames without Sentry relying on the release, dist, or file name. If you're familiar with how compiled languages un-minify stack frames, you'll find artifact bundles function in much the same way, utilizing a concept called Debug IDs (a UUID). For more on why we took this approach, take a look at this new post found on our Sentry engineering blog.

Getting Started

You can access our guide on how to use artifact bundles here.

Limitations

• Only sentry-cli is updated to generate and upload artifact bundles. Meaning, if your application relies on one of our bundler plugin, you'll have to wait a bit longer for this feature to be enabled.
• sentry-cli >= 2.17.0 is required to upload artifact bundles

Feedback Channels

• Sentry Discord Community / #sourcemaps
• Github Issues
• This discussion