v1.9.2 – August 16, 2026
This release improves production error responses, strengthens JWT error handling, and fixes the TypeScript type for needMappers.
- Fixed excessive production response sanitization in
Zod,Joi,express-validator,Mongoose,Prisma, andSequelizemappers - Added separate
JWTmapper handling to prevent sensitive JWT error details from being exposed in production - Fixed the TypeScript type for
needMappers - Updated
README.mddocumentation - Expanded tests for production-safe mapper responses
What does it mean?
Starting with v1.9.2, production responses from supported library mappers are more useful and informative. Previously, some mapper responses were sanitized more aggressively than necessary, which could remove details that were safe to return to API consumers.
Sensitive information is still protected where required, while development mode continues to provide additional details useful for debugging.
JWT errors are now handled separately. This provides stricter control over what information can appear in production responses and addresses a case where sensitive JWT error details could potentially be exposed.
The TypeScript definition for needMappers has also been corrected. It now uses the appropriate union type instead of being typed as a generic string[], improving type safety and editor autocomplete when configuring mappers.
Finally, the documentation has been updated to make several parts of the library clearer, including how NODE_ENV affects error responses, which errors may be thrown by the library itself, and where to find relevant configuration information.
Website: Official documentation ds-express-errors
Website Changelog: Official ds-express-errors Changelog
Website Roadmap: Official ds-express-errors Roadmap
Have an idea? ds-express-errors discussions
Top comments (0)