Source Maps

Sentry supports un-minifying JavaScript via Source Maps. This lets you view source code context obtained from stack traces in their original untransformed form, which is particularly useful for debugging minified code (e.g. UglifyJS), or transpiled code from a higher-level language (e.g. TypeScript, ES6).

Most of the process is the same whether you're using this SDK or the new unified JavaScript Browser SDK, so the main docs for dealing with source maps can be found there. The one difference is how you specify the release in your SDK configuration.

If you are uploading source map artifacts yourself, you must specify the release in your Raven.js client configuration. Sentry will use the release name to associate digested event data with the files you’ve uploaded via the releases API, sentry-cli or sentry-webpack-plugin. This step is optional if you are hosting source maps on the remote server, but still recommended.

Raven.config("your-dsn", {
  release: "my-project-name@2.3.12",

Now that you've specified the release in your SDK config, head on over to our main source maps docs to learn how to create your source maps and make them available to Sentry. There you'll also find a troubleshooting guide.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").