Katie Byers

@Danny-weebo Can you please add the following to your code, right after `Sentry.init()`, and see what shows up in the console? ```js console.log("tracingOrigins:", Sentry.getCurrentHub().getClient()?.getIntegrationById("BrowserTracing") .options.tracingOrigins ); ```

@irkinwork, I notice from your screenshot that your names do _not_ in fact match. If the script that errors is at, say, `file:///a/b/c/script.js`, and in `script.js` the `sourceMappingURL` is `script.map.js`...

Related (would only solve some cases, but would give us an easy fix for anything webpack/vercel-y): https://github.com/vercel/nft/issues/202

> * I think trying to reduce the size of the existing Sentry CLI is the wrong angle of attack: Unnecessary complexity + will grow again when new features are...

Hi, @wereHamster. Thanks for bringing this up. We'll chat as a team to see how we best want to handle this. In the meantime, as a workaround, you can add...

> Do I really have to do it for each request? Can't I call addGlobalEventProcessor just after Sentry.init() ? Yes, and no, unfortunately you can't. I wouldn't be calling it...

Nice, thanks for sharing, @wereHamster!

Hi, @LewisJEllis. Thanks for the info (and a decent laugh at the tweet). We're discussing which option we want to go with, and will need to do a little testing...

> it seems we don’t include this polyfill for the es5 bundle for some reason Yeah, I'll admit that for the sake of expediency I explained it in that PR...

Decided Relay was a better place for this - saves us needing to add the string to our bundle. @zspitzer - Once the PR linked above is released, you'll be...