We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Being able to send to Sentry the error that may happen on the third party scriptthird-party
would like to see this:
<LiveChatLoaderProvider onError: (error) => { Sentry.captureError(throw error) } > <HelpScout /> </LiveChatLoaderProvider>
Yes
there are no alternatives, as it happens on the window (the browser) so it's not caught not even on the ErrorBoundary on the _app on a NextJS app
window
ErrorBoundary
_app
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What problem would this feature solve?
Being able to send to Sentry the error that may happen on the third party scriptthird-party
Describe the solution you’d like to see
would like to see this:
Are you willing to work on implementing this solution?
Yes
Describe alternatives you’ve considered
there are no alternatives, as it happens on the
window
(the browser) so it's not caught not even on theErrorBoundary
on the_app
on a NextJS appAdditional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: