server-error-handling

Standardize server error handling in TypeScript by wrapping errors with predefined ORPC error codes like NOT_FOUND, FORBIDDEN, UNAUTHORIZED, and BAD_REQUEST. This enforces consistent responses across protected routes and services while preventing raw error leakage.

Handle authorization errors in protected ORPC procedures by throwing typed wrappers such as UNAUTHORIZED or FORBIDDEN instead of raw errors. Using shared error enums ensures uniform access-control patterns and consistent server responses across the codebase.

Prevent raw server errors from leaking by consistently wrapping them with ORPC error wrappers in your handlers and services. This approach replaces raw exceptions with predefined typed codes, providing uniform and safe responses to clients.

You can add custom error codes by extending the shared error enums and applying the correct ORPC wrapper in your handlers. The Skill provides integration guidance to reduce boilerplate and mistakes when introducing new access-control or validation patterns.

Throwing raw errors in TypeScript server handlers breaks consistency and risks leaking sensitive information. Wrapping exceptions with typed ORPC codes like BAD_REQUEST enforces a standardized, predictable response format across all protected routes and services.