Sentry uses releases to match the correct source maps to your events. If you're using SystemJS to bundle your project, your should configure SystemJS to generate source maps and use Sentry CLI to create the release and upload the source maps.

1. Update SDK Options

To be able to match Sentry errors with the correct release, you must provide a release property in the SDK options:

  // Make sure this value is identical to the name you give the release that you
  // create below using Sentry CLI
  release: "<release_name>",

2. Generate Source Maps

Next, configure SystemJS to output source maps:

builder.bundle("src/app.js", "dist/app.min.js", {
  minify: true,
  sourceMaps: true,
  sourceMapContents: true,

3. Upload Source Maps Using Sentry CLI

Make sure Sentry CLI is configured for your project. You can use a .sentryclirc file or environment variables:



After configuring Sentry CLI and bundling your project, create a release with Sentry CLI:

sentry-cli releases new <release_name>

Next, upload your release artifacts (source files and source maps):

sentry-cli releases files <release_name> upload-sourcemaps /path/to/files

At this point, the release is in a draft state (“unreleased”). Once all source maps have been uploaded, and your app has been published successfully, finalize the release with the following command:

sentry-cli releases finalize <release_name>

For more information on how to configure releases via Sentry CLI, check out our Sentry CLI release management docs.

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