core-error-handling

Standardized typed error handling is enforced by replacing generic TypeScript Error classes with core errors from @zerobias-org/types-core-js, ensuring consistent error types across HTTP clients, services, and background workers.

Mapping custom API errors to HTTP statuses is achieved by applying specific constructor patterns like InvalidCredentialsError or UnauthorizedError within a central error handling utility that translates core errors into predictable HTTP status codes.

Handling invalid input and rate limit exceeded errors requires using the specific InvalidInputError and RateLimitExceededError constructors from @zerobias-org/types-core-js to ensure predictable error mapping and uniform handling across your codebase.

A central error handling utility is recommended to integrate core errors across HTTP clients and backend logic, providing a starter pattern that maps API responses to appropriate core error constructors for uniform application behavior.

Replacing generic TypeScript Error classes with core errors enforces consistent error types across all modules, providing standardized constructors and predictable HTTP status mappings for safer application logic.

Testing core error handling involves verifying that specific error constructors and the central handling utility correctly map API responses to expected typed core errors, ensuring uniform error handling coverage across the codebase.