Set status to 500 when a function throws

[remorses]

Currently if a function throws the status is 200, it would be cool to set it to 500.

This would make it easier to find the errored request in the network tab

By the way this project is awesome, really great work! ❤️

[Janpot]

I know it's tempting, but for now I don't intend to mix the RPC layer errors with the transport layer errors. I want to reserve 500 status code for unexpected errors in the transport layer e.g. when there's a programming error in the rpc server code somewhere, or a proxy/load-balancer/gateway messing up.

[remorses]

Ok, i will close this for now

[Janpot]

In the longer term I think I could provide some "devtools" as part of this library, similar to react-query.

[Janpot]

This issue keeps coming up so it seems like this is a common pain point amongst users of this library. I will reopen this issue and try to think of a solution. Perhaps a 502 code makes sense with an attempt to parse the content as json and a fallback to the current situation.

[Janpot]

I'm still thinking about status codes for errors, but in the meantime I updated the message format to adhere to JSON RPC. This makes it possible to use tools like JSON RPC Chrome Viewer to introspect the rpc frames that are being transferred by next-rpc.

See also https://github.com/Janpot/next-rpc#debugging-next-rpc