Luca Forstner

I _want_ to be careful especially with the move towards Next.js server actions and all. We could be publishing serverside source code that contains secrets. But yea I wanna do...

Thanks for reporting this and providing repro! Sadly, I don't know a solution to this yet as of now. We tried a million different things to inject necessary code into...

> I'll raise it with webpack-bundle-analyzer in the meantime. Great, thank you!

Hi @valscion, thanks for the insight! We'll leave this issue open in case other people run into this. For now, I still don't have a solution. We need to inject...

> Closing because of lack of details we actually implemented this 😂

Hi, from looking at it it seems that Next.js uses a custom serializer that cannot handle `undefined`. You should always be safe to omit calling `Sentry.init()` no matter what. We...

This warning can be safely ignored. In theory, the SDK should add an ignore rule for this warning. I wonder why that doesn't work for you 🤔 https://github.com/getsentry/sentry-javascript/blob/7e59832817f20becb304b82a05bb555a7f315c6e/packages/nextjs/src/config/webpack.ts#L662-L669 Would you...

@GiancarlosIO It's not really a fix we published but we are ignoring the warning automatically. The code for this is here: https://github.com/getsentry/sentry-javascript/blob/7de5ea40e29125b0092138e419e0a3be20c296d5/packages/nextjs/src/config/webpack.ts#L663 I struggle a bit to understand how this...

@cyrus-za would you mind sharing more information? The import trace would be helpful.

It might be nx that is messing with our ignoring of the warning. @GiancarlosIO are you also using nx? Please note: It is safe to ignore this warning. All it...