-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
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
fix(browser): Guard for this._flushOutcomes
if old BaseClient
s are floating around
#13085
Conversation
…e floating around
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how this happens given that recent versions shouldn't even look at the same global sentry carrier anymore but I have no objections to the fix 😅
size-limit report 📦
|
Co-authored-by: Lukas Stracke <[email protected]>
In that case the error must be at build time, actually, I believe - as the browser client is extending the base client, and it seems (??) that the base client it is extending is not the v8 base client (I guess??) 🤔 |
This rather screams module resolution error then, no? 🤔 |
🤷 possibly? 😅 Always hard to be sure in such cases, but I think it has to be that, because we never call this on another ("random") client, but only on |
Again, I think it's fine to merge this if it helps people. Just surprised that this is happening 😅 |
I kinda don't want to merge this because of reasons outlined in this comment: #13083 (comment) |
Closing bc stale |
Fixes #13083