Readable stack traces in production: source maps + OpenTelemetry

Readable stack traces in production: source maps + OpenTelemetry Two years ago I left Sentry and moved to OpenTelemetry. The one thing I could not replace was source map resolution. OTel collectors do not resolve minified stack traces — that has always been proprietary to Sentry. I built smapped-traces internally to fill that gap. It has been running in production since. We are open sourcing it now that it has stabilized. The problem with naive approaches Serving source maps from your build output exposes your source code publicly. Restricting access requires your error handler to authenticate against a source map server at resolution time, which is complexity you do not want in that path. Bundling source maps into your collector configuration does not work either — the collector has no stable way to associate a map with a minified file across deployments. Debug IDs The approach I landed on uses debug IDs, a mechanism now supported by Turbopack natively and by webpack via the TC39 prop