error-handling

Standardize API error responses in Next.js by wrapping routes with the withErrorHandling middleware and throwing specialized ApiError subclasses to trigger a uniform formatted error envelope. This centralizes handling and ensures consistent response formats.

Handle Zod validation errors by integrating them into the withErrorHandling middleware, which maps schema failures to BadRequestError instances. This converts validation issues into a standardized API error envelope with consistent fields.

Yes, this error handling system works with Convex. The ApiError hierarchy and middleware are designed for modern web apps including Next.js, Convex, and Zod, applying structured error responses to validation, authentication, and not-found scenarios.

You can standardize web API errors using specialized classes including BadRequestError, UnauthorizedError, ForbiddenError, NotFoundError, ConflictError, and InternalServerError. Each extends the base ApiError class with specific status codes.

Return a consistent error envelope from API routes by using the formatErrorEntity function. It structures the ApiError instance into a standardized response format, ensuring clients receive uniform error codes and messages across all endpoints.

Centralized error handling middleware standardizes API responses and improves reliability better than scattered try-catch blocks. It captures thrown ApiError instances uniformly, applies structured logging, and formats a consistent error envelope.