Tim Fish

Yep, I need to update the above ramblings. There's a [more recent issue](https://github.com/getsentry/sentry-javascript/issues/5815) for the tracing changes. > Also, I'd just have all tracing functionality in @sentry/node by default, so...

> could we look into if we can just use globalThis? [Eventually](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis#browser_compatibility), but we'll need to wait for Node.js v12 to be our MSV. And the [Sentry supported browsers](https://docs.sentry.io/platforms/javascript/troubleshooting/supported-browsers/) suggests...

Would it be possible to move the hub code without breaking the public API? We could move the code to `core` and then have `hub` only depend on `core` and...

I've reopened this and it can be closed when `@sentry/hub` is finally deleted and the tests are migrated to core.

I haven't tried your code so I might be completely wrong... but it looks like you've defined the `cy` attribute twice whereas I'm guessing it should be `cx.bind`: ```html ```

Abhi has marked this for v8.0.0 since this is technically a breaking change

I've been actively looking at what changes are required to support other runtimes like Deno with the existing codebase! Until all those changes are complete, I made [this experimental Deno...

Yeah very strange. The stack trace and results from that script don't add up in a way I can fathom. Would love to try out that container! > (And no,...

> I can see that we're setting browser.name as simply "Chrome" and then a chrome tag with a 4-part SemVer value for the Chrome version. I believe the information in...

🤔 just realised this doesn't take into account any modifications to `hint` which is required to add attachments from `beforeSend`...