Async middleware wrapper in Express - Step-by-Step Execution

Concept Flow - Async middleware wrapper

Request comes in

↓

Async middleware wrapper called

↓

Call async middleware function

↓

Promise resolves or rejects

↓

Success

↓

Call next()

↓

Next middleware or route handler

↓

Response sent or error handled

The async middleware wrapper calls an async function and handles its promise. On success, it calls next() to continue. On error, it passes the error to next(err) for Express error handling.

Execution Sample

Express

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

Wraps an async middleware function to catch errors and pass them to Express error handler.

Execution Table

Step	Action	Promise State	Error Caught?	Next Called	Result
1	Request arrives, wrapper called	Pending	No	No	Wrapper starts async function
2	Async function runs, returns Promise	Pending	No	No	Waiting for async completion
3	Promise resolves successfully	Resolved	No	Yes	next() called, continue flow
4	Request handled by next middleware	N/A	No	N/A	Response sent or further processing
5	If async function throws error	Rejected	Yes	Yes	next(err) called, error handler triggered

💡 Execution stops when next() or next(err) is called to continue or handle error.

Variable Tracker

Variable	Start	After Step 2	After Step 3 or 5	Final
fn	async middleware function	async function Promise pending	Promise resolved or rejected	N/A
Promise	undefined	Pending	Resolved or Rejected	Handled by next() or next(err)
error	undefined	undefined	Error object if rejected	Passed to next(err) or undefined

Key Moments - 2 Insights

Why do we need to catch errors in async middleware?

Because async functions return promises, errors inside them won't be caught by Express automatically. The wrapper catches rejected promises and passes errors to next(err), as shown in execution_table step 5.

What happens if we forget to call next() after async success?

The request will hang because Express waits for next() to continue. The wrapper ensures next() is called after promise resolves, as seen in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is next() called after successful async completion?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Check the 'Next Called' column in execution_table rows.

According to variable_tracker, what is the state of the Promise after step 2?

A Rejected

B Pending

C Resolved

D Undefined

💡 Hint

Look at the Promise row and After Step 2 column in variable_tracker.

If the async function throws an error, what does the wrapper do according to execution_table?

A Calls next(err) to pass error

B Calls next() without error

C Ignores the error

D Returns a resolved promise

💡 Hint

See the 'Error Caught?' and 'Next Called' columns in execution_table step 5.

Concept Snapshot

Async middleware wrapper syntax:
const asyncWrapper = fn => (req, res, next) => {
  Promise.resolve(fn(req, res, next)).catch(next);
};

Behavior:
- Calls async middleware function
- Catches rejected promises
- Passes errors to Express error handler via next(err)

Key rule: Always call next() or next(err) to continue Express flow.

Full Transcript

This visual execution shows how an async middleware wrapper works in Express. When a request arrives, the wrapper calls the async middleware function and wraps it in Promise.resolve to handle both sync and async returns. If the promise resolves, next() is called to continue to the next middleware or route handler. If the promise rejects due to an error, the catch block calls next(err) to pass the error to Express's error handling middleware. The execution table traces these steps, showing promise states and when next() or next(err) is called. The variable tracker shows how the async function and promise states change during execution. Key moments clarify why catching errors in async middleware is necessary and the importance of calling next() to avoid hanging requests. The quiz tests understanding of when next() is called, promise states, and error handling behavior. The snapshot summarizes the wrapper syntax and its role in Express middleware flow.