Community Feedback - ds-express-errors

Library version: v1.9.0

Docs version: web-docs v1

Stack: Node.js 18 / Express 5 / TypeScript 5.5 (strict) / Zod 4.4.3

Experience level: Senior

Overall rating: 8/10

"In a new project, yes — without hesitation. Mongoose duplicate-key handling alone is something I've written by hand more times than I want to count, and getting Prisma, JWT and Zod in the same package for zero dependencies is a good trade. In my existing project, probably not, and not because of the library. I already have a handler with tests, and its response shape is what my frontend expects. Migrating would be work with no user-visible benefit. That's a 'when you adopt it' answer, not a quality judgement."

Library version: v1.9.0

Docs version: web-docs v1

Stack: Node.js 26.4 / Express 5.2 / Prisma 7.9 / TypeScript 7 / Zod 4.4.3

Experience level: Junior

Overall rating: 9/10

"Would I use it? I personally found it very easy to use and it is a strong tool. I would use it in the future projects if the maintenance continues to be this active. Would it work for production? I think it would, but it should include the log level configuration built in without needing a logging library to handle it."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js + Express 5 + TypeScript + Mongoose

Experience level: Mid-level

Overall rating: 7/10

" With the two TS typing bugs fixed, yes — for a Node/Express API not already invested in a hand-rolled error-handling layer, this removes real boilerplate and the mapping coverage (Mongoose, Prisma, Sequelize, Zod, Joi, JWT, express-validator) is broader than most alternatives I've used. As it stands today, I'd hold off on a strict-mode TypeScript project until the .d.ts files catch up with the README."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js 25.9 / Express 5.2.1 / strict TypeScript / Zod 4.4.3 / Drizzle ORM + pg / pino / Basic Auth

Experience level: Senior

Overall rating: 7/10

"The core request-error path is small, practical, and genuinely removes boilerplate. I would use the handler, presets, and custom mappers today. I would not yet delegate production validation responses, diagnostics, and process shutdown to the defaults without application-level overrides."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js 24 | Express 4.19 | sequelize-typescript 2.1.6 | TypeScript 5.5.3

Experience level: Beginner

Overall rating: 7/10

"I liked the duck-typed vs strict mode in sequelizeMapper.js"

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js 24 | Express 5.2 | sequelize 6.37.8 | sequelize-typescript 2.1.6 | TypeScript 5.3.3 | Zod 4.4.3

Experience level: Senior

Overall rating: 9/10

"The library solves a useful problem. The setup was simple, standard Express middleware just app.use(...). It was nice to see the library doesn't have any dependencies which made it much easier to review and trust before installing and using it. This is a really big deal with all the 'supply chain attacks' these days and as another reviewer said you don't mention it at all. Nice test coverage, this is also a helpful way to showcase how the software works since every test is basically an example. Overall verdict: this would complement my development practices, mostly I favor using NestJS and this is functionally equivalent to what they consider an exception filter, it would make sense to offer a module providing it in that format."

Library version: v1.9.1

Docs version: README GITHUB

Stack: Node.js 26.7.0 + Express.js 5 + TypeScript + Prisma 7 + PostgreSQL + Zod

Experience level: Senior

Overall rating: 6/10

"The library solves a useful problem and provides ready-made error mapping for common tools such as Prisma and Zod. The current documentation, configuration API, default response format, and several unexpected behaviors make the initial integration and debugging experience less convenient than expected."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node v22.16, Express v5.2.1, TypeScript v7.0.2, Zod v4.4.3

Experience level: Junior

Overall rating: 7/10

"Overall I think the library is going in the right direction: it's easy to get started, it's configurable, and it removes the need to write a custom error handler from scratch on every new project. Getting started was genuinely easy and quick, which matters a lot for adoption."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js + Express.js + TypeScript (strict) + Mongoose + Zod

Experience level: Senior

Overall rating: 6/10

"First impressions were good. Zero dependencies, nothing to generate, no plugin to register. Wire errorHandler last, wrap your async routes, done. Getting a 409 out of a raw E11000 without writing that mapping myself is a real saving, and 409 is the right code where a lot of hand-written handlers just return 400. Mongoose maps without injecting anything, which I did not expect given that errorClasses has keys for Zod, Joi, Prisma and Sequelize but not Mongoose. In a small project, yes. It took very little time to wire up and it removed real boilerplate immediately, and for an internal service the shutdown behaviour would not keep me up at night. In production, not as it stands. The two things I most need from error handling are the stack trace of an unexpected error and field-level validation output for clients, and I lose both. The shutdown issues matter for the same reason: exit 1 on a normal deploy would show up as a failing pod, and a crashed process serving 200s is the kind of thing that turns a small incident into a confusing one. None of this feels fundamental. The bugs are small and specific, the library is honest about being beta, and the roadmap already names the stack trace work. If the original error were preserved and shutdown closed sockets properly, my answer would change. 6/10 for now, and I would happily look at it again in a later version."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js 22.15.0 / Express 5.2.1 / TypeScript 7.0.2 (strict) / Mongoose 9.9.2 / Zod 4.4.3 / jsonwebtoken 9.0.3

Experience level: Mid-level

Overall rating: 7/10

"The core error pipeline is solid and removed real boilerplate for my stack. Most of my deductions are documentation gaps and production response behaviour, not broken fundamentals. New project: yes. Mongoose duplicate-key handling, Zod/JWT mapping, presets, and zero dependencies are a good trade for the setup cost. Production today: with caveats. I would use the handler, presets, and mappers, but I would override or document around production validation messages, and wire monitoring myself until a clearer reporting hook exists."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js (v24, ES Modules) + Express.js (v5.2) + Mongoose (v9.9) + Zod (v4.4) + jsonwebtoken (v9.0)

Experience level: Mid-level

Overall rating: 7.5/10

"The library achieves its primary promise: it provides centralized, type-safe, zero-dependency error management that removes repetitive code from Express apps. The addition of process signal listeners (SIGTERM/SIGINT) and custom mapping hooks makes it flexible. It loses a few points due to minor rough edges in error message formatting strings (particularly JWT and Zod) and the need for deeper documentation examples around TypeScript types for customMappers."

Library version: v1.9.1

Docs version: web-docs v1

Stack: Node.js + Express 5 + TypeScript + Mongoose + Zod + JWT

Experience level: Senior

Overall rating: 8/10

"A solid approach to centralized error handling, best suited for new projects rather than migrations. Would I use this in production? Yes, but mostly for a new project. My test was a migration, since I already had error handling built into my own API starter, and that's exactly where the friction showed up: the asyncHandler problem broke almost every handler I had. Starting from scratch avoids that. The Errors.NotFound hang is the one issue that would make me pause before shipping this to a team, since it fails silently with nothing telling you what went wrong. Everything else is a real but livable gap, and four of the five issues I found already have movement on the roadmap."