feat: Add support for sourcemap debugId
property
#151
+17
−0
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.
Debug IDs are detailed in the TC39 proposal.
Debug IDs are unique IDs generated from a deterministic hash of the source code which are then injected/included in both source and sourcemap. They can be used to easily identify the correct sourcemaps in production.
Although the proposal is only at stage 2, the debug ID in source and sourcemap is well defined and it's only the JavaScript API which is likely to change before stage 3. Sentry already process hundreds of millions of source files per month containing debug ids!
I've recently added support for injecting debug IDs to webpack, Rollup, and Rolldown and wanted to get them working in Rspack too with the same API as webpack.