rethrowing the error in handleReturnedServerError loses the orignal error

[reymondgomera]

I was throwing an error in my backend and then rethrowing it in the handleReturnedServerError function, but for some reason, it loses the original error, such as when I throw a Prisma error.

[TheEdoRan]

Can you provide a link to a minimal reproduction of this issue? Thanks.

[reymondgomera]

I can't provide the link right now, but what I have is a server action. When the server action encounters an error, like a PrismaClientError, I just throw it, and handleReturnedServerError catches it. Inside handleReturnedServerError, you can still access the original error, but when you rethrow it, the client can no longer access the original error—only the name, digest, and message are accessible.

[TheEdoRan]

I've just tested this by setting up a new project with Prisma + SQLite, and the same thing happens with Server Actions that are not defined using next-safe-action, so I'd say that's not a lib related issue.

[reymondgomera]

Hmm.. the server actions that I am using are defined using next-safe-action, though. Were you able to access the original error on the client side? Even when you are just re throwing the error in the handleReturnedServerError() funtion?

[TheEdoRan]

I've tried both ways, an action defined using next-safe-action and a different one which is just an async function. The behavior is the same: code prop gets printed on the server, but is undefined on the client.