Luca Forstner

> I guess I can't use these two things together…? @alimony Correct. In the next major version of the SDK we'll support the new webpack plugin and also hiding source...

As a workaround I think you can try using ``` disableServerWebpackPlugin: true, disableClientWebpackPlugin: true, ``` in next.config.js

@alimony That will disable the webpack plugin that ships internally with the Next.js SDK. Allowing you to use your own instance.

@fmiqbal Please see this thread for potential resolution steps or open a new issue with a reproduction example. Thank you!

@yashsway Yep. Currently, the Next.js SDK depends on the webpack plugin v1. Please make sure that the versions don't collide. This is not something we can influence from within the...

It should be fine to inti the edge SDK with a dynamic import. If possible, try to leave the node SDK init synchronous.

This is actually a good insight. Thanks for raising this! I see this as a documentation issue we need to resolve.

Oh yeah, when creating a custom client you currently have to manually start sessions as they are normally created and in the `Sentry.init()`. We should probably make this part of...

@Patrick-Ullrich would you be able to provide a reproduction example (or maybe even give us access to your project to take a look)? We were unsuccessful in reproducing with @xr0master's...

@xr0master I guess we're not senior enough then 😄