Upload source maps so stack traces stop arriving minified
Stack traces that point at minified bundles, made readable by uploading source maps at build time.
The ticket
Upload source maps during the build so production stack traces resolve to real files and lines.
Acceptance criteria
- A production trace resolves to real file names and line numbers
- Upload happens in the build, keyed to the release
- Source maps are not served publicly
- A seeded production error is checked in the tracker as proof
What lands as proof
A before and after of the same trace: minified column offsets, then real file names and lines.
Why teams defer it
- Everything works in development, where the traces are already readable.
- Publishing source maps by accident is a real risk, so it needs care that turns a config change into a review.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: upload source maps during the build so production stack traces resolve to real files and lines. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a production trace resolves to real file names and line numbers, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.