ref(js): Mention debug ids in sourcemap docs #13646
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 181 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
App Routes Affected:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
lforst
approved these changes
May 9, 2025
Contributor
lforst
left a comment
lforst
left a comment
There was a problem hiding this comment.
Reordering 👍 the note idk.. It especially doesn't solve the feeback in the linked lnear issue.
| <PlatformSection notSupported={["javascript.capacitor", "javascript.cordova"]}> | ||
| <Alert> | ||
|
|
||
| By default, Sentry will link source maps by injecting <PlatformLink to="/sourcemaps/troubleshooting_js/debug-ids/">Debug IDs</PlatformLink> into your build output. Alternatively, there are also <PlatformLink to="/sourcemaps/troubleshooting_js/legacy-uploading-methods/">other methods</PlatformLink> to associate source maps with Sentry that do not require modifying your build output. |
Contributor
There was a problem hiding this comment.
Idk about "by default" here...
| If you want to configure source maps to upload manually, follow the guide for your bundler or build tool below. | ||
|
|
||
| <PlatformSection notSupported={["javascript.capacitor", "javascript.cordova"]}> | ||
| <Alert> |
Contributor
There was a problem hiding this comment.
Not sure I like this note. Feels out of place honestly.
Member
Author
There was a problem hiding this comment.
Hmm I am very open to rephrase this, but IMHO it does make sense to mention here what all the things we are talking about on this page and subpages actually does (=inject debug ids into your build files)?
Contributor
There was a problem hiding this comment.
Actually you're right probably
Contributor
|
@mydea - still want to make this update? |
Member
Author
|
ah, yes I think so, let me resolve conflicts etc (not sure if I get to it today, but I want to eventually!) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
Closes https://linear.app/getsentry/issue/FE-398/user-feedback-debug-ids-tooling