Async middleware wrapper in Express

Introduction

Async middleware wrapper helps handle errors in async Express middleware easily. It avoids repeating try-catch blocks.

When writing async route handlers in Express that use await.

When you want to catch errors from async functions and pass them to Express error handlers.

When you want cleaner code without many try-catch blocks in middleware.

When you want consistent error handling for async middleware.

When building APIs that use async database calls or external requests.

Syntax

Express

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

This is a higher-order function that takes an async function fn and returns a new middleware function.

It runs fn and catches any errors, passing them to next() for Express error handling.

Examples

Basic async wrapper function that catches errors from async middleware.

Express

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

Using asyncWrapper to wrap an async route handler that fetches data.

Express

app.get('/data', asyncWrapper(async (req, res) => {
  const data = await getDataFromDb();
  res.json(data);
}));

Async wrapper used for a POST route creating a user, handling errors automatically.

Express

app.post('/user', asyncWrapper(async (req, res) => {
  const user = await createUser(req.body);
  res.status(201).json(user);
}));

Sample Program

This Express app uses an async middleware wrapper to handle errors in an async route. The route /hello returns JSON after a delay. Errors are caught and sent as JSON error responses.

Express

import express from 'express';
const app = express();
app.use(express.json());

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

// Simulated async function
const getData = async () => {
  return new Promise((resolve) => setTimeout(() => resolve({ message: 'Hello World' }), 100));
};

app.get('/hello', asyncWrapper(async (req, res) => {
  const data = await getData();
  res.json(data);
}));

// Error handler middleware
app.use((err, req, res, next) => {
  res.status(500).json({ error: err.message });
});

app.listen(3000, () => console.log('Server running on port 3000'));

Important Notes

Always use the async wrapper on async middleware to avoid unhandled promise rejections.

The wrapper passes errors to Express's built-in error handler or your custom error middleware.

This pattern keeps your code clean and easier to read.

Summary

Async middleware wrapper catches errors from async functions automatically.

It helps avoid repetitive try-catch blocks in Express middleware.

Use it to keep async route handlers clean and error-safe.

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