Response.clone: Body has already been consumed. Seroval/trpc conflict?
There was some discussion about this recently, but was there a way to fix this currently in user code?
3 Replies
Is this a TRPC error
like the cause of things
The past discussion was failing to serialize TRPC's error, because of a field that references the Request/Response objects
Yes, I guess the solution is to fix trpc errors
But it's there way to somehow safeguard trpc errors
not realistically. I'm not familiar with how trpc works nor if it allows intercepting requests/responses like a middleware