v1.9.0 – July 23, 2026
This release focuses on improving Prisma and Sequelize support, making error detection more reliable while providing clearer development logs.
What's new?
- Added strict
instanceofchecks forPrismaandSequelize - Configuration property
errorClassesnow supportsPrismaandSequelize - Fixed ESM import issue
- Fixed
PrismaClientInitializationErrordetection -
Improved
SequelizeConnectionErrordetection. It now distinguishes between:SequelizeConnectionRefusedErrorSequelizeHostNotFoundErrorSequelizeHostNotReachableErrorSequelizeAccessDeniedError
New development log format
Development logs for Prisma and Sequelize have been improved and now include more useful information.
Library Name (Prisma code if available): [Error Name] followed by the formatted message.
Example:
Prisma P2002: [PrismaClientKnownRequestError] Unique constraint failed: { modelName: User }; { target: email }
Sequelize: [SequelizeAccessDeniedError] Access denied for user...
What does it mean?
Starting with v1.9.0, you can enable advanced Prisma and Sequelize detection by providing the corresponding objects in the errorClasses configuration.
Simply import the original object from the library and pass it to setConfig():
const { Prisma } = require('@prisma/client');
const { Sequelize } = require('sequelize');
setConfig({
errorClasses: {
Prisma,
Sequelize
}
});
Small improvements
ds-express-errors now distinguishes between different SequelizeConnectionError types and maps them individually.
This provides more accurate HTTP responses and more informative development logs when database connection issues occur.
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)