Resolve minified JavaScript with uploaded or hosted source maps, then see exactly why a map did or did not apply.
Your browser runs a bundled, minified version of your code. A source map connects that compressed code back to the original code you wrote. Telebugs uses it to put the original function, file, and line back in the backtrace.
No. Upload them privately with your release and Telebugs will use them without exposing your original source. Already hosting them? Approve the exact public HTTPS origin and Telebugs will fetch them for new reports.
Yes. If your build already uses sentry-cli, point it
at Telebugs and keep the source map step in your deployment.
Starting fresh? You can upload maps from a Telebugs release too.
Keep the deployed files and uploaded maps from the same build.
The source-map
manual covers the upload commands and troubleshooting.
Telebugs shows the map status on the report, so you can tell whether it is still processing, missing, blocked, or failed. Fix the deployment or permission problem and retry it there.
Telebugs groups the received event before source-map processing. Remapping the trace never changes the report’s issue or grouping key.