error-handling

Standardize tRPC error handling by throwing typed TRPCError instances with specific codes like NOT_FOUND or UNAUTHORIZED, and configuring a custom errorFormatter to map these codes to predictable HTTP status responses for clients.

Customize client-facing error payloads in a tRPC backend by implementing a custom errorFormatter, which transforms the default TRPCError output into a structured, predictable format for client applications.

Preserve stack traces in tRPC by wrapping original errors with a cause property when throwing a TRPCError, ensuring rich debugging information remains intact throughout the server-side procedure execution.

Yes, this error handling approach requires the @trpc/server dependency to function, as it relies on the native TRPCError class and the tRPC router's errorFormatter configuration to map HTTP statuses correctly.

tRPC server errors return inconsistent HTTP status codes when procedures lack a custom errorFormatter, making it necessary to standardize TRPCError codes like BAD_REQUEST and INTERNAL_SERVER_ERROR for predictable client responses.

Route global tRPC errors for centralized logging by configuring the onError property within the tRPC router, capturing unhandled TRPCError instances before they reach the custom errorFormatter.