@lforst I am on the latest canary, does this mean this will work without further setup?

You'll need to add the hook in your instrumentation.ts as outlined in this PR description: getsentry/sentry-javascript#12885 (comment)

Any ideas where this is going to reach a stable release? I don't want to switch to canary and just want to have an idea of how much we need to wait for this :)

BTW, and just to be sure, we are not getting errors on Sentry when using server actions and I'm assuming that it's related with this issue too. Do you know if that's the case?

@giovannibenussi I think this will hit stable at the same time when next@15 lands which is dependent on react@19 but I'll let the Vercel folks confirm that :)

As far as server actions go, as of now (assuming you're not using the new hook yet) you need to manually wrap server actions in Sentry.withServerActionInstrumentation().

Hey, right, we're not using the hook because we don't want to switch to canary.
I didn't know about the Sentry.withServerActionInstrumentation function. I tested it and works as expected, thanks for suggesting that, we'll be using it until the hook reaches a stable release!

No this wouldn't replace the captureException calls in the error.ts files. This hook only applies to the server side and error.ts is entirely client side.

cool, that sounds good. we currently re-throw a custom error in our fetch helper in order to capture server errors so would be great to remove that logic ! excited for the release of this 🥳