Luca Forstner

Honestly, I am also lost. If anybody could share reproduction I can take a closer look.

@camillevingere if you have an error.tsx down the line, it will swallow the error, yes. It's the same as adding an error boundary or a try-catch somewhere.

But please try to put together a reproduction example I can take a look at. `error.tsx` is only responsible for the client-side, not server.

@camillevingere sure thing!

@camillevingere yes, nothing in particular stood out to me. I don't know how to properly deploy your app which I would need to do in order to reproduce the issue....

@camillevingere This is on our radar. This issue is not p0 for us as of now. We will get to it at some point.

I can't reproduce this bug with your app because it doesn't build due to env vars not being set. Please provide a minimal reproduction example so we can take a...

I think we can close this now that we set `onlyIncludeInstrumentedModules` by default.

This is very likely because webpack is consuming a lot of memory generating sourcemaps. You can set the following in version `8.x`: ```js module.exports = withSentryConfig(nextConfig, { sourcemaps: { disable:...

Pretty sure you can provide the env var in the interface you configure the build script with :thinking: