Working with Next.js RSC Error digests

[stephanie-anderson]

[lforst]

This needs upstream changes from React so we can work with it:

• Let us pass a custom digest or error ID of some sort that is propagated to the client.
• Let us determine the digest for an error on the server directly.

A sort-of workaround for this is proper distributed tracing which let's people approximate what errors correlate.

[steebchen]

Just to clarify, this means that the actual error is not caught at all, right? I experimented a bit with it but it seems that just the frontend error is reported but not the actual thrown error on the backend at all. Is this correct? If so, maybe it would be best to create another issue to track these errors in the first place, as this issue is about connecting these two errors, which would be the next step. I'd be happy to create a new issue. Or am I missing something?

[lforst]

@steebchen No this issue is about being able to correlate Client errors caused by Server Component errors. My PR to Next.js should make this a bit easier at least: vercel/next.js#64256

If the SDK is not collecting backend errors for you, please open a new issue with reproduction steps. Thank you!