Why are my async errors not caught in Express 4?
Express 4 does not catch promise rejections from async handlers. Wrap with asyncHandler that catches and calls next(err). Or upgrade to Express 5, which catches async errors automatically.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Common Routing Mistakes in Express (and How to Avoid Them)
Routes in wrong order (wildcards first), middleware without next(), handler without response, wrong mount path, same path with different methods, async errors not caught, GET for non-idempotent actions, inconsistent status codes, no versioning, and all routes in app.js.
Probably a wildcard route is declared before them. Express matches in declaration order, so /users/* catches /users/me before /users/me can. Fix: declare specific routes before wildcards.
A middleware forgot to call next() or a handler forgot to send a response. Every middleware must call next() or respond; every handler must respond or pass to next(err). No orphans.
Still have questions?
Browse all our FAQs or reach out to our support team