-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Rework sourcemap troubleshooting session for debug IDs #7049
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework sourcemap troubleshooting session for debug IDs #7049
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2df06d7 to
e1c0e0b
Compare
…emap-troubleshooting-section
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
shanamatthews
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Little tweaks to follow our style guide and make this more readable
| <Note> | ||
|
|
||
| Alternately you can specify which files to upload. For example: | ||
| Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier. | |
| Sentry recently updated our tooling to make the process of uploading source maps easier. |
|
|
||
| Alternately you can specify which files to upload. For example: | ||
| Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier. | ||
| We recommend you upgrade your tooling to the newest versions, as that is usually easier than to troubleshoot the legacy method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| We recommend you upgrade your tooling to the newest versions, as that is usually easier than to troubleshoot the legacy method. | |
| If you're using an older version of the Sentry SDK (version 7.47.0 or older), we recommend upgrading your tooling and switching to the new source maps process, as it is easier to troubleshoot than the legacy method. |
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
src/platform-includes/sourcemaps/troubleshooting/javascript.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>
|
@shanamatthews those were amazing suggestions. Thank you! 🙏 Just to vibe check my changes a bit: As a person not working on the source map process, do the instructions somewhat make sense to you? Ideally, I would like to get rid of, or even better, improve, all the sections that make somebody go "what the f do they want from me here". |
I gave the current source map troubleshooting page a pass and updated it for the new debug ID process.
Disclaimer: We'll probably run into issues with debug IDs in the future which we don't know of yet. The current troubleshooting page is probably not very in-depth but I am planning to extend it whenever users run into issues.