The translation works automatically as long as your JavaScript files and source maps are reachable via HTTP(S).
If your build tool generates source maps and deploys them alongside your JavaScript bundles, no additional configuration is required.
If your source maps are hosted behind authentication, you can configure a Source Map Integration to provide credentials (Basic Auth, Bearer token, or custom headers) for specific URL prefixes.
What’s included:
- Automatic translation of minified JavaScript stack traces
- Support for public and authenticated source maps
- URL prefix–based integration configuration
- Per-frame translation with detailed error feedback
- Original stack trace always preserved
Each frame in a stack trace is translated independently. If a frame cannot be resolved, it remains in its original form and shows a warning icon. Hovering over the icon reveals the reason (for example, missing source map, authentication error, or file not found).
You can switch between the original and translated stack trace at any time using the toggle in the UI.
