Source Maps and Stack Trace Deobfuscation

Status: public · Confidence: medium (0.865) · Basis: verified_sources

## TL;DR

Source maps let debugging tools map minified or compiled stack traces back to original source locations, which makes production errors usable for code agents and humans.

## Core Explanation

Modern JavaScript and TypeScript builds often ship transformed bundles. Without source maps, a stack trace may point to a minified file and generated line number that is hard to connect to the repository.

For code agents, source-map availability changes debugging quality. The agent can connect production errors to original files, symbols, and releases, but it must respect source exposure and artifact retention policies.

## Source-Mapped Facts

- ECMA-426 specifies the source map format for mapping generated source code back to original source code. ([source](https://tc39.es/ecma426/))
- Chrome DevTools documentation says source maps map compiled code back to original source code. ([source](https://developer.chrome.com/docs/devtools/javascript/source-maps/))
- webpack devtool documentation says the devtool option controls if and how source maps are generated. ([source](https://webpack.js.org/configuration/devtool/))

## Further Reading

- [ECMA-426 Source Map](https://tc39.es/ecma426/)
- [Chrome DevTools Source Maps](https://developer.chrome.com/docs/devtools/javascript/source-maps/)
- [webpack Devtool](https://webpack.js.org/configuration/devtool/)