Uh oh!
There was an error while loading. Please reload this page.
fix(replay): Better guard for logger.info - #8873
Conversation
Not sure if/why this should be required, but better safe then sorry I guess... Hopefully fixes#8741
There was a problem hiding this comment.
I wouldn't go through with this change. There is no way this is doing anything except bloating unless there is something really really funky going on.
I'd rather look into situations where logger may be undefined. (i.e. accessing it without having the utils package loaded for some reason)
mydea
commented
Aug 28, 2023
Honestly I am also not clear why/how this is happened, but it def. started happening once we replaced __DEBUG_BUILD__&&logger.info()`
// becameif(!__DEBUG_BUILD__){return;}logger.info()To me it appears that this should be the same thing, but 🤷 . To be clear this is happening for us on sentry.io as well: https://sentry.sentry.io/issues/4387494961/?project=11276&referrer=github_integration so it cannot be related to a build issue. I strongly suspect it is related to some browser extension stuff or similar, but it's hard to say. As it happens for users too, we should somehow guard against this. Feels hacky, but 🤷 But yeah, maybe it is cleaner to do |
My suspicion is that this is happening with multiple sentry instances on the same page. (browser extensions) |
Maybe it is related to this...
mydea
commented
Aug 28, 2023
OK, I rewrote this to use |
size-limit report 📦
|
billyvg
left a comment
There was a problem hiding this comment.
Might be helpful to log what info is when it is not a function
mydea
commented
Aug 30, 2023
Closing in favor of #8880, which maybe/hopefully also fixes this. |
Not sure if/why this should be required, but better safe then sorry I guess...
Hopefully fixes#8741