Luca Forstner

Hi, we updated the logic for this. Can you check if that fixed this issue?

I don't think we will ever get to this since the pages router is gonna phase out anyhow.

We can think about blocking requests for source maps with Next.js rewrites automatically.

Hi, thanks for writing in! It's awesome that you provided logs! This line: ``` Sentry Logger [log]: Sending outcomes: [ { "reason": "network_error", "category": "transaction", "quantity": 1 } ] ```...

I am not aware of any issues like this in the SDK. Would you mind sharing a small reproduction example that lets us reproduce this behaviour? As an intermediary step,...

Please check you followed the setup here to set up react rendering errors: https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#report-react-component-render-errors Since otherwise your setup is pretty much what we tell you to do in the docs...

@arnaudjnn Ah thanks for that! I wrote down a task for myself to mention this in the docs and in the wizard setup.

Opened https://github.com/getsentry/sentry-wizard/pull/544 and https://github.com/getsentry/sentry-docs/pull/9306 to better document this interaction.

@kunzeleric Please see https://github.com/getsentry/sentry-javascript/issues/8869#issuecomment-1695355649

@realkosty I remember telling @vicainelli to use multiple clients. Moving forward (also thinking about future SDK versions), having multiple clients in MFRE situations is definitely beneficial. My mental model is...