v1.8.0 – January 11, 2026
- Added support for user-provided error classes in custom mappers (Zod, Joi)
- Added support for turning only needed mappers in config
- Rate limiting logger
- Express-validator mapper fix incorrect logic
- Expand prisma errors ['
P2005',P2006,P2007,P2011,P2027] - updated mongoose & sequelize mappers check
What is mean?
Starting with version v1.8.0+, you will be able to choose which mappers to enable so as not to use unnecessary ones, reducing the cost of checking unnecessary mappers.
This version also adds the ability (currently only with Zod and Joi) to pass library classes via setConfig for more rigorous verification. By default, the ds-express-errors library uses duck typing verification, which in turn allows it to remain dependency-free. The ability to pass your own error classes preserves this feature of the library.
Previously, the library's built-in loggers did not have a rate limit, which could cause crashes and freezes.
Small improvements:
New Prisma errors have been added, and the verification logic has been improved in some mappers.
Also, starting with this update, the built-in loggers support colour output for easier reading.
v1.8.1 – January 12, 2026
- Fixed missing api import for
logDebug -
maxLoggerRequestsnew property in config to set maximal log rate requets per 1 minute (default100) - Added check for
BigIntfor internalsafeStringifymethod - Fixed incorrect status code in mongoose mapper
- Fixed incorrect status code in sequelize mapper
- Logger refactor for
customLogger - Added
Errors.GatewayTimeout(message) - Fix mapping sequileze now correct map:
-
SequelizeOptimisticLockError, -
SequelizeEmptyResultError, -
SequelizeDatabaseError, SequelizeConnectionErrorSequelizeTimeoutError
-
Website: Official Changelog
Website: Official documentation ds-express-errors
Website Changelog: Official ds-express-errors Changelog
Website Roadmap: Official ds-express-errors Roadmap
Have a idea?: ds-express-errors discussions
Top comments (0)