T
tRPC

Feature or happy accident: error message from `cause` being used as TRPC's error message

Feature or happy accident: error message from `cause` being used as TRPC's error message

Aaryzing
View on Discord
11/1/2023
When a procedure throws a TRPC error with no message, it turns out that if the thrown error has a cause, and the cause has a message, the cause's message will be used as the TRPC error message returned to the client. Is this on purpose or an accident? Couldn't find this behavior documented.

Looking for more? Join the community!

T
tRPC

Feature or happy accident: error message from `cause` being used as TRPC's error message

Join Server
Recommended Posts
When error in tRPC route, the error message is vaugeThere are no line numbers when a runtime error happens in a tRPC route. Surely I am missing somethinHow to have 2 separate trpc clients for http and websockets?I'm trying to have a setup where I can use trpc with 2 separate clients, one for normal HTTP requestHow to configure context for a standalone server?Are there any examples out there on how to set up context for a standalone server? The docs do incluDocs hard to follow with so much `next` codeNot having a great experience with the docs. There are many examples that use `next`, making it hard