Async middleware wrapper in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of an async middleware wrapper in Express?

It helps handle errors in asynchronous middleware functions by catching rejected promises and passing errors to Express's error handler automatically.

beginner

Why do we need to wrap async middleware functions in Express?

Because Express does not catch errors from async functions by default, wrapping ensures errors are caught and passed to next() for proper handling.

intermediate

Show a simple example of an async middleware wrapper function.

const asyncWrapper = fn => (req, res, next) => { fn(req, res, next).catch(next); };

intermediate

How does the async middleware wrapper improve code readability?

It removes the need for try-catch blocks inside every async middleware, making code cleaner and easier to maintain.

beginner

What happens if an error occurs inside an async middleware wrapped by the async wrapper?

The error is caught by the wrapper and passed to Express's next() function, triggering the error-handling middleware.

Why do we use an async middleware wrapper in Express?

A To speed up middleware execution

B To catch errors from async functions and pass them to Express error handlers

C To convert middleware to synchronous functions

D To log all requests automatically

Async middleware wrapper catches rejected promises and forwards errors to Express error handlers.

What does the async middleware wrapper function return?

A A synchronous middleware function

B A promise that never resolves

C A function that calls the async middleware and catches errors

D An error object

It returns a function that executes the async middleware and catches any errors to pass to next().

Which Express function is used to pass errors to the error handler?

A next()

B res.send()

C req.end()

D app.use()

Calling next() with an error passes control to Express's error-handling middleware.

What problem does the async middleware wrapper solve?

A It automatically retries failed requests

B Express cannot handle synchronous middleware

C It prevents middleware from running

D Express does not catch errors from async middleware by default

Express does not handle rejected promises in async middleware unless wrapped.

Which of these is a correct usage of an async middleware wrapper?

A app.get('/route', asyncWrapper(async (req, res) => { /* code */ }));

B app.get('/route', async (req, res) => { /* code */ });

C app.get('/route', (req, res) => { /* code */ });

D app.get('/route', asyncWrapper(() => { /* code */ }));

The async middleware wrapper wraps an async function to catch errors properly.

Explain why an async middleware wrapper is important in Express and how it works.

Think about error handling in async functions inside Express middleware.

Write a simple async middleware wrapper function and describe how to use it in an Express route.

Focus on the function signature and error catching.

Practice

1. What is the main purpose of using an async middleware wrapper in Express?

easy

A. To automatically catch errors from async route handlers without try-catch blocks

B. To convert synchronous middleware into asynchronous functions

C. To speed up the execution of middleware functions

D. To log all requests automatically

Solution

1. Step 1: Understand async middleware challenges

   Async route handlers can throw errors that need to be caught to avoid crashing the app.

2. Step 2: Role of async middleware wrapper

   The wrapper automatically catches errors from async functions and passes them to Express error handlers, avoiding manual try-catch blocks.

3. Final Answer:

   To automatically catch errors from async route handlers without try-catch blocks -> Option A

4. Quick Check:

   Async error catching = To automatically catch errors from async route handlers without try-catch blocks [OK]

Hint: Async wrapper catches errors, no manual try-catch needed [OK]

Common Mistakes:

• Thinking it converts sync to async
• Assuming it improves speed
• Confusing it with logging middleware

2. Which of the following is the correct syntax to create an async middleware wrapper function in Express?

easy

A. const wrap = fn => (req, res, next) => { try { fn(req, res, next); } catch (err) { next(err); } };

B. const wrap = fn => (req, res, next) => fn(req, res, next).catch(next);

C. const wrap = fn => async (req, res, next) => { await fn(req, res, next); };

D. const wrap = fn => (req, res, next) => { fn(req, res, next).then(next); };

Solution

1. Step 1: Understand async wrapper pattern

   The wrapper returns a function that calls the async function and catches errors with .catch(next).

2. Step 2: Check each option

   const wrap = fn => (req, res, next) => { try { fn(req, res, next); } catch (err) { next(err); } }; uses try-catch but misses async/await and won't catch async errors properly. const wrap = fn => (req, res, next) => fn(req, res, next).catch(next); correctly returns a function that calls fn and catches errors with .catch(next). const wrap = fn => async (req, res, next) => { await fn(req, res, next); }; awaits but does not catch errors. const wrap = fn => (req, res, next) => { fn(req, res, next).then(next); }; calls then(next) which is incorrect for error handling.

3. Final Answer:

   const wrap = fn => (req, res, next) => fn(req, res, next).catch(next); -> Option B

4. Quick Check:

   Async wrapper uses .catch(next) = const wrap = fn => (req, res, next) => fn(req, res, next).catch(next); [OK]

Hint: Async wrapper uses .catch(next) to handle errors [OK]

Common Mistakes:

• Using try-catch without async/await
• Not returning the wrapped function
• Misusing .then instead of .catch

3. Given the code below, what will be the output when a GET request is made to /data?

const express = require('express');
const app = express();

const wrap = fn => (req, res, next) => fn(req, res, next).catch(next);

app.get('/data', wrap(async (req, res) => {
  const data = await Promise.resolve('Hello World');
  res.send(data);
}));

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

app.listen(3000);

medium

A. Nothing, request hangs

B. Error caught

C. Hello World

D. SyntaxError

Solution

1. Step 1: Analyze the async route handler

   The async function resolves 'Hello World' and sends it as response.

2. Step 2: Check error handling

   No error occurs, so the error middleware is not triggered. The wrapper ensures errors would be caught if any.

3. Final Answer:

   Hello World -> Option C

4. Quick Check:

   Successful async response = Hello World [OK]

Hint: No error means normal response sent [OK]

Common Mistakes:

• Assuming error middleware always runs
• Thinking async wrapper changes output
• Confusing promise resolution with error

4. Identify the error in the following async middleware wrapper code:

const wrap = fn => (req, res, next) => {
  try {
    fn(req, res, next);
  } catch (err) {
    next(err);
  }
};

medium

A. fn should not receive next as argument

B. Using try-catch inside middleware is not allowed

C. next(err) should be replaced with throw err

D. Missing async keyword and await, so async errors are not caught

Solution

1. Step 1: Understand async error handling

   Async functions return promises; errors inside them are caught via .catch or await with try-catch.

2. Step 2: Analyze the wrapper code

   The wrapper calls fn without await or .catch, so errors inside async fn are not caught by try-catch.

3. Final Answer:

   Missing async keyword and await, so async errors are not caught -> Option D

4. Quick Check:

   Async errors need await or .catch = Missing async keyword and await, so async errors are not caught [OK]

Hint: Try-catch alone misses async errors without await [OK]

Common Mistakes:

• Thinking try-catch works without await
• Confusing next(err) with throw
• Believing next should not be passed

5. You want to create an async middleware wrapper that also logs the error message before passing it to Express error handler. Which of the following implementations correctly achieves this?

hard

A. const wrap = fn => (req, res, next) => fn(req, res, next).catch(err => { console.error(err.message); next(err); });

B. const wrap = fn => async (req, res, next) => { try { await fn(req, res, next); } catch (err) { next(err.message); } };

C. const wrap = fn => (req, res, next) => { fn(req, res, next).then(() => {}, err => { console.log(err); }); };

D. const wrap = fn => (req, res, next) => { try { fn(req, res, next); } catch (err) { console.error(err); next(err); } };

Solution

1. Step 1: Understand error logging and forwarding

   We want to log the error message and then pass the full error to next() for Express to handle.

2. Step 2: Evaluate each option

   const wrap = fn => (req, res, next) => fn(req, res, next).catch(err => { console.error(err.message); next(err); }); uses .catch to log err.message and calls next(err) correctly. const wrap = fn => async (req, res, next) => { try { await fn(req, res, next); } catch (err) { next(err.message); } }; passes err.message to next, which breaks error handling. const wrap = fn => (req, res, next) => { fn(req, res, next).then(() => {}, err => { console.log(err); }); }; logs error but does not call next, so error is not forwarded. const wrap = fn => (req, res, next) => { try { fn(req, res, next); } catch (err) { console.error(err); next(err); } }; uses try-catch without async/await, so async errors may be missed.

3. Final Answer:

   const wrap = fn => (req, res, next) => fn(req, res, next).catch(err => { console.error(err.message); next(err); }); -> Option A

4. Quick Check:

   Log then next(err) in .catch = const wrap = fn => (req, res, next) => fn(req, res, next).catch(err => { console.error(err.message); next(err); }); [OK]

Hint: Log error inside .catch, then call next(err) [OK]

Common Mistakes:

• Passing err.message to next instead of err
• Not forwarding error to next
• Using try-catch without async/await