Francesco Gringl-Novy

I think this is hopefully fixed, let's close this for now.

> I don't know how easy it will be to track this down in case it doesn't reproduce in other Next.js apps but I can assist with that. For now...

Hmm, so I added some tests for this specifically here: https://github.com/getsentry/sentry-javascript/pull/11830 and it seems to be working as expected 🤔 Look here: https://github.com/getsentry/sentry-javascript/pull/11830/files#diff-846c22f3c13c0f21374988eda6e64f0c844b2ba8c6561360b9050427b918faeeR70 This shows that `level: 'log'` for `console.trace`....

Just to clarify, you are using nodePolyfills in you svelte browser app? What's the reason/background on this? I would guess that the node polyfill is overwriting something on the text...

So without having any further context I would suspect that you should _probably_ not use nodePolyfill but instead transpile your code with a common JS plugin or something like this...

So this is tricky to debug from the distance, but overall I believe `rollup-plugin-polyfill-node` is not supposed to run in the browser 🤔 So whatever needs this should probably also...

At this point, I think we'd need a repro to be able to dig further into this. Without this, I fear there isn't a lot we can do to figure...

Hmm, that's interesting of course. So the fix would be to basically _not_ reset this when replay ends 🤔 cc @billyvg, what are your thoughts on this?

HI @amc6, could you share more details in how you ran into this? We do not document `import Sentry from '@sentry/xxx'` anywhere (because it does not work), and our TS...

Hmm, that kind of sucks 😅 So, if this is the same issue as with `requestAnimationFrame`, it is only relevant to do this in rrweb functions that are related to...