Luca Forstner

We could also add a `postinstall` script in the package.jsons that checks for this Edit: After thinking about this a bit, it's probably not the best of ideas to have...

Another idea: We could send meta-information on this to Sentry so we can display some warnings directly in the interface.

@ndom91 For now you could try not calling `Sentry.init()` in `sentry.server.config.js` and removing all the `import`s there, or you could uninstall the Next.js package and use `@sentry/browser` instead. Both are...

> How about having these as named exports? @sentry/tracing, @sentry/tracing/browser and @sentry/tracing/node? Shouldn't it be `@sentry/browser/tracing` instead of `@sentry/tracing/browser`? So we can depend on `@sentry/browser` from within `@sentry/browser/tracing`. Maning the...

Continued thread over in more recent issue here: https://github.com/getsentry/sentry-javascript/issues/5815#issuecomment-1258309921

Hi @filips123, thanks for reporting these issues, and thank you for providing such detailed explanations. We will take a look!

To help me debug this, what have you set the `trackComponents` and `hooks` options to in `createTracingMixins()`?

Hi everybody, we attempted to fix this in https://github.com/getsentry/sentry-javascript/pull/5918 which got released in version `7.15.0` of the SDK. Would you mind trying out the new version and report back whether...

Hi again, we released version [7.16.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.16.0) which may contain a fix (related https://github.com/getsentry/sentry-javascript/issues/5917). May I ask you again to try it out? Thank you!

@filips123 Amazing. Thanks for checking! I will close this issue. Feel free to ping me here if any new issues come up!