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

Last updated: July 5, 2026

Resolve Stack Traces with Source Maps

Learn what source maps are, how translation works in Dash0, and how to troubleshoot translation errors.

Dash0 can automatically translate minified JavaScript stack traces back to their original source locations using source maps.

What Are Source Maps

When JavaScript is shipped to browsers it is typically bundled and minified — all variable names shortened and all code collapsed into a single line. This makes stack traces from production errors nearly impossible to act on. For example, an error in your monitoring may look like:

JavaScript
1
at onClick (https://example.com/static/js/main.b1510333.chunk.js:1:1559)

With source maps enabled, Dash0 automatically resolves this into the original source location:

JavaScript
1
at onClick (ProductDetails.js:26:11)

How It Works

Dash0 uses source maps to perform this translation. Source maps are files generated by your build tool that record a mapping from each position in a minified file back to the original source file, line, and column.

When Dash0 receives a web event containing a JavaScript stack trace, it:

  1. Parses each line of the stack trace.
  2. Downloads the referenced JavaScript file.
  3. Reads the //# sourceMappingURL= comment near the end of the file to locate the source map.
  4. Downloads the source map file.
  5. Resolves each minified line and column back to the original source location.

The original stack trace is always preserved unchanged. Translation happens automatically — no code changes are needed in your application.

View Translations

When a stack trace is translated, Dash0 displays the translated version by default in the attributes list. You can switch between the translated and original stack trace at any time using the toggle next to the attribute name.

The original stack trace is always preserved, so you never lose access to the raw minified output.

Partial Translations

If a frame could not be translated, the original minified line is kept in the output and a warning icon is shown next to the frame. Hovering over the icon shows the reason the translation failed.

ErrorAction
JavaScript file not found (404)Verify the file is deployed and a source map integration covers its URL.
Access denied (403) / Authentication required (401)Add a source map integration with the correct credentials. Applies to both the JavaScript file and the source map.
Request timeout / Network errorCheck that the file is reachable from the collector.
JavaScript file too large / Source map file too largeSplit your bundle into smaller chunks to reduce file sizes.
No source map reference found in JavaScript fileConfigure your build tool to embed a //# sourceMappingURL= comment in the output.
Source map not found (404)Deploy the .js.map file at the URL referenced by sourceMappingURL.
Could not parse source mapVerify your build tool is generating a valid source map file.
Position not found in source mapThe source map has no mapping for this location. This can happen if the source map was generated from a different build than the deployed file.
Could not download JavaScript file / Could not load source mapAn unexpected error occurred — contact Dash0 support if this persists.

Further Reading

  • About Web Events. Describes the browser.error event type that carries the stack traces translated by source maps.
  • Set Up the Web SDK. Installation instructions for the Dash0 Web SDK that captures JavaScript errors with stack traces for source map translation.
  • Set Up Source Map Integration. Configure credentials for fetching source maps from private or authenticated CDN endpoints.