Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Conflicting Sentry integration
See original GitHub issueThe way in which Sentry is integrated into this project is conflicting with our React application’s Sentry configuration.
I think there are at least two issues, which might be related:
-
This scope configuration seems to be overriding all of our application’s Sentry context as described in https://github.com/getsentry/sentry-javascript/issues/3206.
As mentioned in
@sentry/minimal’s usage documentation:it is discouraged to interfere with the event context. If for some reason your library needs to inject context information, beware that this might override the user’s context values
Is this scope configuration necessary? Would it be possible to add configuration to disable this behavior?
-
Your dependency on
@sentry/minimal@5.12.0makes it impossible for us to upgrade to Sentry v6 as described in https://github.com/getsentry/sentry-javascript/issues/3234#issuecomment-772968903.While this is a known challenge with competing Sentry instances on a page, would it be possible to upgrade
@sentry/minimalto at leastv5.27.0?
I’m happy to help out with both of the issues above. Let me know what you think, and thanks in advance for your cooperation!
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi, this one will be added to next release
Update for this was released yesterday, can you confirm that its working ok now ?