Skip to content

Conversation

@billyvg
Copy link
Member

@billyvg billyvg commented Oct 12, 2023

Allow callbackWrapper to attach an optional __source__ property to a caught exception. This will allow downstream errorHandlers to decide to re-throw an exception based on the source type.

Needed to address getsentry/sentry-javascript#9170

…ty to exceptions

Allow `callbackWrapper` to attach an optional `__source__` property to a caught exception. This will allow downstream errorHandlers to decide to re-throw an exception based on the source type.
@billyvg billyvg requested a review from mydea October 12, 2023 18:07
@billyvg billyvg marked this pull request as ready for review October 12, 2023 18:08
Comment on lines +33 to +35
if (errorSource) {
error.__source__ = errorSource;
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this only happens if we have errorHandler defined, this probably only affects us. I opted to make this generic so that errorHandler be the source of truth vs attaching a meta property like __allowThrow__

billyvg added a commit to getsentry/sentry-javascript that referenced this pull request Oct 12, 2023
NOTE: This requires a bump to rrweb library

Fixes an issue where the Replay integration can potentially break applications that use `styled-components`. `styled-components` [relies on an exception being throw](https://github.com/styled-components/styled-components/blob/b7b374bb1ceff1699f7035b15881bc807110199a/packages/styled-components/src/sheet/Tag.ts#L32-L40) for CSS rules that are not supported by the browser engine. However, our SDK suppresses any exceptions thrown from within rrweb, so `styled-components` assumes that an unsupported rule was inserted successfully and increases a rule index, which causes following inserted rules to fail due to an out-of-bounds error.

getsentry/rrweb#111 introduces a change the adds metadata to exceptions that occur when calling `insertRule`, and this PR will re-throw those exceptions that will then bubble up to `styled-components`.

Fixes #9170
@billyvg
Copy link
Member Author

billyvg commented Oct 12, 2023

Actually, we probably don't need this as we should just re-throw error in our Replay SDK.

@billyvg billyvg closed this Oct 12, 2023
@mydea mydea deleted the fix-insert-rule-catching-errors branch October 13, 2023 06:57
mydea pushed a commit to getsentry/sentry-javascript that referenced this pull request Oct 13, 2023
NOTE: This requires a bump to rrweb library

Fixes an issue where the Replay integration can potentially break applications that use `styled-components`. `styled-components` [relies on an exception being throw](https://github.com/styled-components/styled-components/blob/b7b374bb1ceff1699f7035b15881bc807110199a/packages/styled-components/src/sheet/Tag.ts#L32-L40) for CSS rules that are not supported by the browser engine. However, our SDK suppresses any exceptions thrown from within rrweb, so `styled-components` assumes that an unsupported rule was inserted successfully and increases a rule index, which causes following inserted rules to fail due to an out-of-bounds error.

getsentry/rrweb#111 introduces a change the adds metadata to exceptions that occur when calling `insertRule`, and this PR will re-throw those exceptions that will then bubble up to `styled-components`.

Fixes #9170
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants