fix(debugIds): Always instantiate global Error
class in debugId injection snippet
#2132
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 makes a small change to the JavaScript snippet that's injected into user files to set the debugId.
Previously, we'd instantiate
new Error
in the script, which usually implicitly instantiatesglobalThis.Error
. However, if users or frameworks would create their ownError
class in the very file where the debugId snippet is instantiated,new Error
would of course take the user-created class rather than the global one. To fix this, this PR now explicitly instantiates theglobalThis.Error
class.fixes: getsentry/sentry-javascript-bundler-plugins#593