Vakt360
NorskSign inStart free
How-to

Upload source maps for readable stack traces

Minified production bundles turn stack traces into gibberish. Source maps let Vakt360 resolve every frame back to your original file, function and line.

How-to · 4 min read

  1. Set a release in your SDK

    Give each deploy a unique release identifier so Vakt360 can match errors to the exact build, and to the maps you upload for it.

    ts
    Sentry.init({
  dsn: "https://<your-key>@ingest.vakt360.com/<project>",
  release: "my-app@1.2.3",
});

  2. Build with source maps enabled

    Make sure your bundler emits .map files for the production build. Most bundlers produce them with a single sourcemap option in the build config.

  3. Upload the maps for that release

    Upload your source maps from the Releases area of your project in the dashboard, or from your build pipeline, so they're attached to the matching release.

  4. Native mobile symbols

    For native mobile, upload an Android ProGuard/R8 mapping file or an iOS dSYM from the project's settings, so native crashes are symbolicated too.

  5. Verify

    Trigger an error from the release you uploaded and confirm the stack trace now shows your original source instead of minified frames.

Related guides

Next.js →

Set up Sentry-compatible error monitoring in your Next.js app with Vakt360. Install the SDK, point it at your DSN, and see grouped, symbolicated errors in minutes.

React →

Set up Sentry-compatible error monitoring in your React app with Vakt360. Install the SDK, point it at your DSN, and see grouped, symbolicated errors in minutes.

React Native →

Set up Sentry-compatible error monitoring in your React Native app with Vakt360. Install the SDK, point it at your DSN, and see grouped, symbolicated errors in minutes.

Start monitoring on the free plan

100,000 events a month, no card required. Point your existing SDK at Vakt360 and see your first event in minutes.

Start freeRead the docs