Luca Forstner

what does it say when you click "unminify code" in the Sentry error?

@a1245582339 there has to be some issue in your self-hosted instance. Most likely Sentry and symbolicator aren't able to communicte. That's the only scenario I can see here.

> So I want to know why the debugId can not inject by webpack plugin? Is there any configuration error on my part? Maybe. We would need reproduction to check.

@realkosty I think a separate function is more clear for now in terms of functionality. I don't think we should overload the `multiplexedTransport` with functionality. I cleaned your draft up...

I think the naming of the function sucks but I will merge this in. We can rename or alias later.

Well find a better name. Currently I don't have ideas.

I don't want to fully dismiss this but I also want to say that setting `sideEffects: false` is wrong when you use the Sentry SDK, as the SDK is essentially...

@jpulec Fair suggestion. Where would you have put the docs exactly so you would have seen it? Also, if you don't mind me asking, why did you add `sideEffect: false`...

@jpulec Thank you. I'll make sure it will get added to the docs after our Next.js migration this week!

Adding onto this: If you want my complete honesty, I would probably recommend to use `sentry-cli` instead of the Sentry esbuild plugin. Esbuild is really not designed to have plugins...