warflash•2mo ago

How to prevent leaking error messages to client?

Hey everyone! I noticed that TRPC seems to log quite extensive error codes in the response body of failed requests, even in production builds. I really don't want my users to be able to see e.g. Error: connect ECONNREFUSED 10.1.0.6:5432\n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)\n Thanks!

No description

2 Replies

infodusha•2mo ago

you can write a middleware that with catch your errors and rethrow them with less info

SiNONiMiTY•2mo ago

this error stack is not visible when you set NODE_ENV="production"

Move Fast & Break Nothing. End-to-end typesafe APIs made easy.

4.9KMembers

View on Discord

More Posts

TRPC NUXT req run 2 times(on server and client)Hi everyone, I have a problem using DataCache in SSR. I am using this function to "GET" my plan. But 405 errorthis is my set up useUtils().setQueriesData should not take input as param.In react query spec, setQueriesData takes filters and updater as parameters. For me it does not make client unable to infer output typesI'm using v11 of trpc in tandem with drizzle on my backend. The client is a react native app. I've s How to access the request body in the onError callback?Hi 👋 I'm having trouble getting the request's body (probably plain text) when the following error Make meta in react-query type-safe.So right now I have to write something like ```typescript *.useQuery({}, { meta: { mfa: false Using tRPC (createCallerFactory) with react-query.Hey guys. Do you know any recipe that would make that approach possible? I'm receiving following e Losing type-safety with merged routersWhen using router exported from an external file, I lose any sort of type safety for the procedures