Error-handling middleware signature in Express - Step-by-Step Execution

Concept Flow - Error-handling middleware signature

Request received

↓

Middleware chain

↓

Error occurs?

No→Next middleware

Yes↓

Error-handling middleware

↓

Send error response

↓

End request

This flow shows how Express passes requests through middleware and routes, and when an error occurs, it jumps to the error-handling middleware to send a response.

Execution Sample

Express

app.use((err, req, res, next) => {
  console.error(err.message);
  res.status(500).send('Something broke!');
});

This code defines an error-handling middleware that logs the error message and sends a 500 response.

Execution Table

Step	Middleware Type	Arguments	Error Present?	Action Taken	Response Sent
1	Normal middleware	(req, res, next)	No	Call next middleware	No
2	Route handler	(req, res, next)	Yes (error passed)	Skip to error middleware	No
3	Error-handling middleware	(err, req, res, next)	Yes	Log error and send 500 response	Yes: 'Something broke!'
4	End	-	-	Request ends after response	Yes

💡 Error-handling middleware sends response, stopping further middleware.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
err	undefined	undefined	Error object	Error object	Error object
req	Request object	Request object	Request object	Request object	Request object
res	Response object	Response object	Response object	Response object with status 500	Response sent
next	Function	Function	Function	Function	Not called after error middleware

Key Moments - 2 Insights

Why does error-handling middleware have four arguments instead of three?

Because Express identifies error-handling middleware by the presence of the first 'err' argument, as shown in the execution_table step 3 where the middleware signature is (err, req, res, next).

What happens if you forget to include the 'err' parameter in error middleware?

Express will treat it as normal middleware and not call it on errors, so errors won't be handled properly, as seen in step 2 where error skips normal middleware.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Express detect an error and jump to error-handling middleware?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Error Present?' and 'Action Taken' columns in execution_table rows.

According to variable_tracker, what is the value of 'err' after Step 1?

A Error object

B undefined

C null

D String message

💡 Hint

Look at the 'err' row under 'After Step 1' in variable_tracker.

If the error-handling middleware did not call res.status(500).send(), what would happen?

A The request would hang without response

B Express would automatically send a 404 response

C The next middleware would handle the error

D The error would be ignored and request continues

💡 Hint

Refer to execution_table step 3 and step 4 about response sending and request ending.

Concept Snapshot

Error-handling middleware in Express has 4 arguments: (err, req, res, next).
It catches errors passed from previous middleware or routes.
Use it to log errors and send error responses.
If missing 'err', Express won't treat it as error middleware.
Always end with sending a response or calling next(err).

Full Transcript

In Express, error-handling middleware is special because it has four parameters: err, req, res, and next. When an error happens in normal middleware or routes, Express skips normal middleware and jumps to the error-handling middleware. This middleware can log the error and send a response like status 500. If you forget the 'err' parameter, Express won't recognize it as error middleware, so errors won't be caught properly. The flow starts with request, goes through middleware, and if an error occurs, it jumps to error middleware which sends the response and ends the request.