tRPCttRPC
Powered by
warflashW
tRPC•2y ago•
3 replies
warflash

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 
Error: connect ECONNREFUSED 10.1.0.6:5432\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)\n 


Thanks!
image.png
tRPCJoin
Move Fast & Break Nothing. End-to-end typesafe APIs made easy.
5,015Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?

Similar Threads

Translated error messages
Answer OverflowAAnswer Overflow / ❓-help
3y ago
How to access TRPCClientError error path client-side?
Answer OverflowAAnswer Overflow / ❓-help
15mo ago
Prevent client tsc from typechecking the server
🦊�🦊 / ❓-help
15mo ago
Server actions leaking .env
juanJjuan / ❓-help
10mo ago