NAre you throwing a TRPCError?
NIs there some reason you can’t use that?
NThrows have type safety so don’t worry about that
NThe global errorFormatter is probably what you want, check instanceof your own error class, then turn it into the “shape” you want including error code
NBut also this is RPC, thinking too much in http codes is the wrong mindset, passing back a code with similar meanings is fine, you can even return a “valid” response with an error key if you like, just throwing is the more standard approach
NThe need for logging is totally valid
NI assume you've read the docs, but you can set your error codes in tRPCError, might be able to set that within the errorFormatter too, but definitely can handle errors and do some bespoke logging for your infra needs
https://trpc.io/docs/error-handling
https://trpc.io/docs/error-formatting
https://trpc.io/docs/error-handling
https://trpc.io/docs/error-formatting
Whenever an error occurs in a procedure, tRPC responds to the client with an object that includes an "error" property. This property contains all the information that you need to handle the error in the client.
The error formatting in your router will be inferred all the way to your client (& React components)
