Async error handling in routes in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why do we need special error handling for async routes in Express?

Because async functions return promises, errors inside them won't be caught by Express's default error handler unless we pass errors to next(). We need to handle errors explicitly to avoid unhandled promise rejections.

beginner

What does the 'next' function do in Express route handlers?

The 'next' function passes control to the next middleware or error handler. When called with an error, it triggers Express's error handling middleware.

intermediate

How can you catch errors in async route handlers without try/catch blocks everywhere?

You can create a wrapper function that catches errors from async functions and passes them to next(), so you don't repeat try/catch in every route.

beginner

Show a simple example of an async route handler with error forwarding using next().

app.get('/data', async (req, res, next) => {
  try {
    const data = await getData();
    res.json(data);
  } catch (err) {
    next(err); // Pass error to Express error handler
  }
});

intermediate

What is the benefit of using an async error handler wrapper function in Express?

It reduces repetitive try/catch blocks in each route, making code cleaner and easier to maintain by automatically forwarding errors to Express's error handler.

What happens if an error occurs inside an async route handler but you don't call next(err)?

A The error is ignored and the request hangs or crashes the server.

B The error is logged but the response continues normally.

C Express automatically catches the error and sends a response.

D The server restarts automatically.

Without calling next(err), Express does not catch async errors automatically, which can cause the request to hang or crash.

Which of these is a common pattern to handle async errors in Express routes?

A Returning errors directly from the async function.

B Ignoring errors and letting the server crash.

C Using synchronous code only.

D Using try/catch inside each async route and calling next(err) on error.

Using try/catch and calling next(err) ensures errors are passed to Express's error handler.

What does a wrapper function for async error handling do?

A It wraps async functions and automatically catches errors to pass to next().

B It converts async functions to synchronous ones.

C It logs errors but does not forward them.

D It disables error handling.

The wrapper catches errors from async functions and forwards them to Express error middleware.

How do you define an Express error handling middleware?

A A middleware with two parameters: (req, res).

B A middleware with four parameters: (err, req, res, next).

C A middleware with three parameters: (req, res, next).

D A middleware with one parameter: (err).

Error handling middleware in Express must have four parameters to catch errors.

Which of these is NOT a good practice for async error handling in Express?

A Using a centralized error handler middleware.

B Wrapping async routes to catch errors automatically.

C Ignoring errors inside async routes.

D Calling next(err) when catching errors.

Ignoring errors can cause unhandled rejections and unstable server behavior.

Explain how to handle errors in async Express routes and why it's important.

Think about how Express handles errors and what happens with promises.

Describe how to create a reusable wrapper function for async error handling in Express routes.

Focus on wrapping async functions to catch errors automatically.

Practice

1. What is the main reason to use try/catch blocks inside async route handlers in Express?

easy

A. To automatically retry failed requests

B. To catch errors from asynchronous code and pass them to Express error handlers

C. To make the route handler run faster

D. To prevent the server from starting

Solution

1. Step 1: Understand async errors in Express routes

   Async functions can throw errors that are not caught automatically by Express, so we need to catch them manually.

2. Step 2: Use try/catch to handle errors

   Wrapping async code in try/catch allows catching errors and passing them to Express with next(error).

3. Final Answer:

   To catch errors from asynchronous code and pass them to Express error handlers -> Option B

4. Quick Check:

   try/catch in async routes = catch async errors [OK]

Hint: Use try/catch to catch async errors and call next(error) [OK]

Common Mistakes:

• Ignoring errors in async functions
• Not calling next(error) inside catch
• Assuming Express catches async errors automatically

2. Which of the following is the correct syntax to pass an error to the next middleware in an async Express route?

easy

A. res.send(error)

B. throw error

C. return error

D. next(error)

Solution

1. Step 1: Identify how Express handles errors

   Express expects errors to be passed to the next middleware using next(error).

2. Step 2: Confirm correct syntax in async routes

   Inside a catch block, calling next(error) forwards the error to the error handler middleware.

3. Final Answer:

   next(error) -> Option D

4. Quick Check:

   Pass errors with next(error) [OK]

Hint: Use next(error) to forward errors in Express [OK]

Common Mistakes:

• Using throw instead of next(error) inside async catch
• Returning error instead of passing to next
• Sending error directly with res.send inside catch

3. Consider this Express route handler:

app.get('/data', async (req, res, next) => {
  try {
    const result = await fetchData();
    res.json(result);
  } catch (error) {
    next(error);
  }
});

What happens if fetchData() throws an error?

medium

A. The error is caught and passed to the next error handler middleware

B. The server crashes immediately

C. The request hangs without response

D. The error is ignored and response is sent anyway

Solution

1. Step 1: Analyze the try/catch block

   If fetchData() throws, the catch block runs and calls next(error).

2. Step 2: Understand Express error flow

   Calling next(error) sends the error to Express error handler middleware, preventing crashes or hanging.

3. Final Answer:

   The error is caught and passed to the next error handler middleware -> Option A

4. Quick Check:

   Errors in try/catch + next(error) = handled error [OK]

Hint: Errors in async try/catch go to next(error) middleware [OK]

Common Mistakes:

• Assuming server crashes on async error
• Thinking response is sent despite error
• Not using next(error) to handle errors

4. Identify the error in this async Express route handler:

app.get('/user', async (req, res, next) => {
  const user = await getUser();
  res.json(user);
});

What is the problem with this code regarding error handling?

medium

A. It sends response twice

B. It incorrectly uses next() inside the route

C. It lacks a try/catch block to handle errors from the async function

D. It uses synchronous code inside async function

Solution

1. Step 1: Check for error handling in async code

   The async function getUser() might throw errors, but no try/catch is used.

2. Step 2: Understand Express error propagation

   Without try/catch and calling next(error), errors will not be handled properly and may crash the server.

3. Final Answer:

   It lacks a try/catch block to handle errors from the async function -> Option C

4. Quick Check:

   Async routes need try/catch for error handling [OK]

Hint: Always wrap async code in try/catch to handle errors [OK]

Common Mistakes:

• Omitting try/catch in async route handlers
• Expecting Express to catch async errors automatically
• Not calling next(error) inside catch

5. You want to create a centralized error handler middleware in Express that catches all errors passed by next(error). Which of the following is the correct way to define this middleware?

hard

A. app.use((err, req, res, next) => { res.status(500).json({ message: err.message }); });

B. app.use((req, res, next) => { res.status(500).send('Error'); });

C. app.get('/error', (err, req, res) => { res.send(err); });

D. app.use((err, req, res) => { res.json({ error: err }); });

Solution

1. Step 1: Recall Express error handler signature

   Error handlers must have four parameters: (err, req, res, next).

2. Step 2: Check each option for correct signature and response

   app.use((err, req, res, next) => { res.status(500).json({ message: err.message }); }); uses all four parameters and sends JSON with error message and status 500, which is correct.

3. Final Answer:

   app.use((err, req, res, next) => { res.status(500).json({ message: err.message }); }); -> Option A

4. Quick Check:

   Error handler middleware = 4 params + send error response [OK]

Hint: Error middleware needs 4 params: err, req, res, next [OK]

Common Mistakes:

• Missing the 'next' parameter in error middleware
• Using app.get instead of app.use for error handler
• Not setting status code in error response