getsentry / getsentry/sentry

Source Map Debugger Modal: Special Case Syntax Errors for Debug IDs

Open
#91,222 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

Syntax errors will cause debug IDs not to be added because the JS crashes in the evaluation phase, which is before the debug ID snippet on top of the file can run.

The good thing is that if you have a syntax error, you likely don’t even want your code to be source mapped, because you want the actual syntax to be shown, not the original code before transpilation.

I think it would make a lot of sense to explain this to users in the source map debugger modal when we see an error with type "SyntaxError".

Contributor guide

Open the contributing guide

Research direction

Start at the source map debugger modal and trace how errors with type "SyntaxError" are displayed. Confirm the existing error-handling path, then make the modal explain why source mapping is unavailable and why the original syntax is shown; done means the explanation appears for syntax errors without changing other error behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.