node-error-handling

Asynchronous error handling in Node.js Express middleware requires wrapping async operations to catch Promise rejections and forward them to error-handling middleware. This Skill provides patterns for managing async errors using custom middleware to prevent application crashes.

Structuring custom error classes in TypeScript backend services involves defining specific error types like ValidationError or NotFoundError for better categorization. This Skill demonstrates implementing these custom classes to ensure errors are properly typed, logged, and returned with appropriate HTTP status codes.

Managing unhandled Promise rejections in a Node.js backend requires implementing global rejection handlers to catch uncaught async errors. This Skill provides code examples for promise rejection management, ensuring unexpected asynchronous failures are caught and logged to maintain service resilience.

Yes, this Node.js error handling approach works with Zod for validation by utilizing TypeScript and Zod to validate inputs and throw structured ValidationError exceptions. It integrates Zod validation failures directly into the custom error class hierarchy for consistent error responses.

Implementing structured logging for application errors in Express involves using the Pino dependency to log detailed error metadata. This Skill provides patterns for structured logging, ensuring that when a NotFoundError or ValidationError is thrown, the error details are systematically recorded for debugging.