Luca Forstner

@mdugue We'll tackle turbopack when it becomes somewhat stable.

## Update As of now, we cannot transfer the functionality we currently have in the SDK to Turbopack: Turbopack loaders are not passed transpiled javascript, instead, they are passed the...

@Stanzilla Turbopack will not work with the SDK (dev and prod). My branch does not contain any fixes or features, just experiments proving that things don't work.

I would love to get rid of the Sentry SDK's dependency on build tooling (i.e. Webpack and Turbopack) entirely. The reason we need to rely on Webpack at the moment...

I think we are slowly moving into a world where we can think about getting rid of all of our reliance on webpack. These are the following features we use...

@mydea when you're back

I feel like this is related to https://github.com/getsentry/sentry-javascript/issues/9874 and most likely has to do with the fact that when you create the logger stream (which is also creating the breadcrumbs)...

Can you share what other Parts of the SDK you used and in what order? You may need to wrap your middleware in `Sentry.withIsolationScope(() => ...))`.

Generally looks good. I think whatever the baseLogger is doing might lose the async context that isolates requests.

Hi, do you mind reporting this issue in the Nx repository? We cannot do anything from within the SDK to work around Nx's module resolution rewriting. In theory Nx should...