Luca Forstner

I really think this happens because you are accidentally bundling code that is intended to run in Node.js into the client bundle. Try to make sure that nothing in your...

I will take a look!

To give an update here: I think this is kind of a big oversight on our end, and Sentry should report these errors. However, when I tried to come up...

@davidbarratt Correct. If you want to be super brave, you can use the latest Next.js canary and do what we do here: https://github.com/getsentry/sentry-javascript/blob/4d61a6db447a3b523fde60390d77046237dc3c27/dev-packages/e2e-tests/test-applications/nextjs-15/instrumentation.ts#L13 We worked with the Vercel team to...

Correct! This is solved by upgrading to Next.js 15 and adding ```ts // instrumentation.ts import * as Sentry from '@sentry/nextjs'; export const onRequestError = Sentry.captureRequestError; ``` to `instrumentation.ts`.

I think this would be very valuable to add as an opt-in option.

We will likely not add a callback for anything because that is too much API surface but a flag that will attach response bodies to events.

Hacking this in is going to be hard. I suggest waiting for official support from our SDK. This is likely gonna happen near- to medium term.

> Don't mean to nag, but what do near and medium term mean to you? We're likely going to have to move away from sentry due to the lack of...

> Hmm, interesting! I wonder if Vercel will add an option to generate sourcemaps... We are in talks with them but progress is rather slow. We have this issue open:...