Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 5, 2026

Set Up Source Map Integration

Configure Dash0 to fetch source maps for translating minified JavaScript stack traces. This guide covers public asset requirements and how to set up integrations for private or authenticated CDN endpoints.

Requirements

  • You are using the Dash0 Web SDK to capture browser errors.
  • Your build tool generates source maps and embeds a //# sourceMappingURL= reference in the minified JavaScript output. This is the default for tools like Webpack, Vite, esbuild, and Rollup.
  • Your JavaScript files and source maps are reachable via HTTP(S) either publicly or via a source map integration. Integrations let you configure credentials for private or authenticated assets — your end users will never have access to them.

If stack traces are not being translated, verify that all three requirements above are met. Per-frame errors are shown directly in the UI — see Partial Translations.

Public Assets

If your JavaScript files and source maps are publicly accessible, translation works out of the box — no additional configuration is needed beyond deploying the .js.map files alongside your JavaScript files.

Make sure the .js.map file is deployed at the URL referenced by sourceMappingURL. Relative URLs are resolved against the JavaScript file's URL; absolute URLs and inline source maps (data:application/json;base64,...) are also supported.

For private or authenticated assets, create a source map integration to provide Dash0 with the right credentials. Source maps do not need to be public — you can keep them behind authentication so your end users never have access to them.

Create an Integration

To configure Dash0 to fetch source maps from authenticated endpoints, follow these steps.

  1. Navigate to Settings → Integrations
  2. Click on Add Integration and select Source Map
  3. Give it a Display Name
  4. Under URL Prefixes, add the base URL of your JavaScript assets — for example https://cdn.example.com/static/js/. Every stack trace URL that starts with this prefix will use this integration's credentials.
  5. Choose an Authentication method:
    • Basic Authentication — username and password.
    • Bearer Token — token value sent as Authorization: Bearer <token>.
  6. Optionally add Custom Headers for any additional request headers your CDN requires.

You can create multiple integrations to cover different environments or URL prefixes. For example, one integration for https://cdn.example.com/ and another for https://staging.example.com/.

Further Reading

  • Set Up the Web SDK. Installation instructions for the Dash0 Web SDK that captures JavaScript errors with stack traces for source map translation.
  • Resolve Stack Traces with Source Maps. Explains how source map translation works and how to troubleshoot errors when stack traces cannot be resolved.