Luca Forstner

As for > ⚠️ What happens for pages with no data fetchers? Should `_app` have a different helper? (no name for transaction) Thinking about what was said in the last...

@abhishek871 @JUDE-EQ Usually these errors originate from browser extensions that your users are using. You can filter these out with the `denyUrls` option: https://docs.sentry.io/platforms/javascript/configuration/filtering/#decluttering-sentry

> This solved my issue, but my Sentry.captureException seem to not get received in my dashboard even though they get sent. > https://github.com/getsentry/sentry/issues/67630#issuecomment-2030701029 @alexandredepape seems like you solved it?

Ah right, okay. Yeah, the browser SDK will not work inside a worker context. I have building a worker SDK on my mental roadmap but no clue when we will...

@alexandredepape I mean it's possible that it works, but there is no guarantee that it will not crash in some way. Inside the `@sentry/browser` package we generally assume that we...

Sup. We released a fix yesterday that will mark the unresolved stack frames as "irrelevant". Currently, we don't upload these "first load JS" files because they usually don't really contain...

This should be fixed in recent versions of the SDK. Feel free to ping us if this is not the case!

I tried getting `uncaughtExceptionMonitor` to work but it basically boils down to what https://github.com/elastic/apm-agent-nodejs/issues/2367#issuecomment-1670408202 outlines perfectly: - When an exception happens, Node.js will not wait for any requests kicked off...

I am gonna mark this as resolved with https://github.com/getsentry/sentry-javascript/pull/11532. This will be shipped as a breaking change as part of the upcoming major v8 release. Please see the migration docs...

We need reproduction in order to fix this.