如何让自定义Express错误中间件在报错时正常运行并返回JSON响应？

Hey there! Let's get your error handler middleware working properly with throw new Error() in Express. The core issue here usually boils down to how Express handles synchronous vs asynchronous errors—especially when you're using async/await in your route handlers. Let's break this down step by step.

First, confirm your middleware setup is correct #

Your error handler looks solid—it has the required 4 parameters (err, req, res, next) and you've placed it at the end of your middleware stack (after all routes), which is exactly what you need. That part isn't the problem.

The key issue: Async route handlers don’t auto-pass errors to Express #

If your route handlers are using async/await, throwing an error inside them won’t automatically trigger your error middleware. Why? Because async functions return a Promise, and Express (pre-v5) doesn’t automatically catch Promise rejections. You need to explicitly pass the error to next(err) for Express to hand it off to your error handler.

Fix 1: Wrap async logic in try/catch #

The simplest way is to wrap your async code in a try/catch block, then pass any caught errors to next():

// Example route handler in goalRoutes.js or userRoutes.js
router.get('/', async (req, res, next) => {
  try {
    // Your async logic here (e.g., database calls)
    throw new Error("Oops, something went wrong!"); // Test error
  } catch (err) {
    next(err); // Pass error to your custom middleware
  }
});

Fix 2: Use an async handler wrapper (cleaner approach) #

To avoid repeating try/catch blocks everywhere, create a reusable wrapper function that automatically catches errors from async routes and passes them to next():

// Create this utility function (e.g., in utils/asyncHandler.js)
const asyncHandler = (fn) => (req, res, next) => {
  Promise.resolve(fn(req, res, next)).catch(next);
};

// Use it in your routes
router.get('/', asyncHandler(async (req, res) => {
  throw new Error("Test error from async route"); // This will now trigger your middleware
}));

Fix 3: Upgrade to Express 5 (if possible) #

Express 5 automatically catches Promise rejections from async route handlers, so you won’t need the try/catch or wrapper—throwing an error directly will work out of the box. Just note that Express 5 is still in beta at the time of writing, so weigh the tradeoffs before upgrading.

Testing synchronous errors #

For non-async (synchronous) route handlers, Express should automatically catch thrown errors and pass them to your middleware. Test this with a simple route:

router.get('/sync-error', (req, res) => {
  throw new Error("Synchronous test error");
});

If you hit this endpoint, your errorHandler should log "running error handler middleware" and return the JSON response as expected.

Verify no other middleware is blocking the error flow #

Double-check that none of your earlier middleware are catching errors and not calling next(err). For example, if you have a middleware that does try/catch but doesn’t pass the error along, it’ll prevent your custom handler from running.

Final check #

After applying one of the async error handling fixes, test your route again. You should see the console log from your error handler, get the JSON response with the error message, and your app won’t crash anymore.

内容的提问来源于stack exchange，提问作者Jacexecaj