Centralized error handling in Node.js - Step-by-Step Execution

Concept Flow - Centralized error handling

Start Request

↓

Execute Middleware/Route

↓

Error Occurs?

No→Send Response

Yes↓

Pass Error to next()

↓

Centralized Error Handler

↓

Send Error Response

↓

End Request

This flow shows how errors in Node.js apps are caught and passed to a single error handler that sends the response.

Execution Sample

Node.js

app.get('/data', (req, res, next) => {
  if (!req.query.id) {
    next(new Error('ID missing'));
  } else {
    res.send('Data for ' + req.query.id);
  }
});

This code checks if 'id' is in query; if missing, it passes an error to the centralized handler.

Execution Table

Step	Action	Condition	Result	Next Step
1	Request to /data with no id	req.query.id undefined	Error created: 'ID missing'	Call next(error)
2	next(error) called	Error passed	Skip normal handlers	Centralized error handler called
3	Centralized error handler runs	Receives error	Sends 500 response with error message	Request ends
4	Request to /data with id=5	req.query.id = '5'	No error	Send response 'Data for 5'
5	Response sent	N/A	Request ends normally	End

💡 Execution stops after sending response or error response to client.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
req.query.id	undefined	undefined	undefined	undefined	undefined
error	none	Error('ID missing')	passed to next()	received in handler	handled
response status	none	none	none	500	sent
response body	none	none	none	'ID missing'	sent

Key Moments - 2 Insights

Why do we call next(error) instead of sending the response directly?

Calling next(error) passes the error to the centralized handler, keeping error logic in one place (see execution_table step 2). Sending response directly would duplicate error handling.

What happens if no error occurs in the route?

The route sends the normal response and the centralized error handler is not called (see execution_table step 4 and 5).

Visual Quiz - 3 Questions

Look at the execution table, what is the response status code sent when an error occurs?

A 404

B 500

C 200

D 302

💡 Hint

Check the 'response status' variable in variable_tracker after step 3.

At which step does the centralized error handler get called?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Next Step' column in execution_table after step 2.

If req.query.id is present, what happens according to the execution table?

A Error is created and passed

B Centralized error handler runs

C Response with data is sent

D Request ends with error

💡 Hint

See steps 4 and 5 in execution_table for normal flow.

Concept Snapshot

Centralized error handling in Node.js:
- Use next(error) to pass errors
- Define one error handler middleware
- Error handler sends error response
- Keeps error logic in one place
- Normal routes send responses if no error

Full Transcript

Centralized error handling in Node.js means when an error happens in a route or middleware, you call next(error) instead of sending a response directly. This passes the error to a special error handler middleware defined once in your app. This handler receives the error and sends a proper error response to the client, like a 500 status with a message. If no error occurs, the route sends the normal response and the error handler is not called. This approach keeps your error handling code in one place, making your app easier to maintain and debug.

Practice

1. What is the main benefit of centralized error handling in a Node.js Express app?

easy

A. It keeps all error handling code in one place for easier maintenance.

B. It automatically fixes all errors without developer input.

C. It prevents any errors from occurring in the app.

D. It makes the app run faster by skipping error checks.

Solution

1. Step 1: Understand centralized error handling purpose

   Centralized error handling means managing errors in one place instead of scattering code everywhere.

2. Step 2: Identify benefits of centralized error handling

   This approach makes the app easier to maintain and debug because all error logic is together.

3. Final Answer:

   It keeps all error handling code in one place for easier maintenance. -> Option A

4. Quick Check:

   Centralized error handling = easier maintenance [OK]

Hint: Centralized means one place for all errors [OK]

Common Mistakes:

• Thinking it prevents errors automatically
• Believing it makes the app faster by skipping errors
• Confusing centralized handling with error fixing

2. Which of the following is the correct signature for an Express centralized error handling middleware?

easy

A. function errorHandler(req, res, next) { ... }

B. function errorHandler(err, req, res, next) { ... }

C. function errorHandler(err, req, res) { ... }

D. function errorHandler(req, res) { ... }

Solution

1. Step 1: Recall Express error middleware signature

   Express error middleware must have four parameters: error, request, response, next.

2. Step 2: Match the correct function signature

   Only the function with (err, req, res, next) matches the required signature.

3. Final Answer:

   function errorHandler(err, req, res, next) { ... } -> Option B

4. Quick Check:

   Error middleware = 4 params (err, req, res, next) [OK]

Hint: Error middleware always has 4 parameters [OK]

Common Mistakes:

• Using 3 parameters instead of 4
• Omitting the error parameter
• Confusing normal middleware with error middleware

3. Given this Express app code snippet, what will be the response when a GET request to '/' throws an error?

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

app.get('/', (req, res) => {
  throw new Error('Oops!');
});

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

app.listen(3000);

medium

A. The server crashes and no response is sent.

B. The client receives a default Express error page with status 404.

C. The client receives 'Error caught: Oops!' with status 500.

D. The client receives 'Oops!' with status 200.

Solution

1. Step 1: Identify error throwing in route

   The GET '/' route throws an error with message 'Oops!'.

2. Step 2: Check error middleware handling

   The error middleware catches the error and sends a 500 status with message 'Error caught: Oops!'.

3. Final Answer:

   The client receives 'Error caught: Oops!' with status 500. -> Option C

4. Quick Check:

   Thrown error caught by middleware = 500 response [OK]

Hint: Thrown errors go to error middleware response [OK]

Common Mistakes:

• Assuming server crashes on thrown error
• Expecting status 404 instead of 500
• Thinking error message is sent without prefix

4. What is wrong with this Express error handling middleware?

app.use((err, req, res) => {
  res.status(500).send('Error: ' + err.message);
});

medium

A. It is missing the 'next' parameter, so Express won't recognize it as error middleware.

B. It should not use res.status(500) inside error middleware.

C. The error parameter should be named 'error' instead of 'err'.

D. It should be placed before route handlers, not after.

Solution

1. Step 1: Check middleware parameters

   Express error middleware requires four parameters: err, req, res, next.

2. Step 2: Identify missing parameter

   This middleware has only three parameters, missing 'next', so Express treats it as normal middleware, not error handler.

3. Final Answer:

   It is missing the 'next' parameter, so Express won't recognize it as error middleware. -> Option A

4. Quick Check:

   Error middleware must have 4 params (err, req, res, next) [OK]

Hint: Error middleware always needs 4 parameters [OK]

Common Mistakes:

• Thinking parameter names must be specific
• Believing status code usage is wrong
• Placing middleware order incorrectly

5. You want to create a centralized error handler that logs errors and sends JSON responses with status and message. Which code snippet correctly implements this in Express?

hard

A. app.use((err, req, res, next) => {
res.sendStatus(200);
});

B. app.use((req, res, next) => {
console.error('Error occurred');
res.status(500).json({ error: 'Unknown error' });
});

C. app.use((err, req, res) => {
console.log(err);
res.send('Error happened');
});

D. app.use((err, req, res, next) => {
console.error(err.stack);
res.status(err.status || 500).json({ error: err.message });
});

Solution

1. Step 1: Verify error middleware signature and logging

   The correct snippet uses four parameters (err, req, res, next) and logs the error stack with console.error(err.stack).

2. Step 2: Check response format and status code

   It sends a JSON response with the error message and sets the status to err.status || 500.

3. Step 3: Evaluate other options

   The other options lack the proper signature, correct logging, status handling, or JSON response.

4. Final Answer:

   app.use((err, req, res, next) => { console.error(err.stack); res.status(err.status || 500).json({ error: err.message }); }); -> Option D

5. Quick Check:

   Proper error middleware logs and sends JSON with status [OK]

Hint: Error middleware: 4 params, log error, send JSON with status [OK]

Common Mistakes:

• Missing 'next' parameter in middleware
• Sending status 200 on error
• Not sending JSON response format