Centralized error handling in Node.js - Mini Project: Build & Apply

Centralized Error Handling in Node.js

📖 Scenario: You are building a simple Node.js server that responds to client requests. To keep your code clean and easy to maintain, you want to handle all errors in one place instead of repeating error handling in every route.

🎯 Goal: Create a Node.js server using Express that has centralized error handling. You will set up a route that can cause an error, then create an error handler middleware to catch and respond to errors in a friendly way.

📋 What You'll Learn

Create an Express app with one route /error that throws an error

Add a variable PORT set to 3000

Use a try-catch block or next() to pass errors to the error handler

Create an error handling middleware function with four parameters: err, req, res, next

Send a JSON response with status and message from the error handler

Start the server listening on PORT

💡 Why This Matters

🌍 Real World

Centralized error handling helps keep server code clean and consistent. It makes debugging easier and improves user experience by sending clear error messages.

💼 Career

Most Node.js backend jobs require knowledge of Express and error handling to build reliable APIs and web servers.

1

Set up Express app and route

Create a variable express by requiring 'express'. Then create a variable app by calling express(). Finally, create a route /error on app that throws a new Error with the message 'Something went wrong!'.

Node.js

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

// Create /error route that throws an error
// Your code here

Hint

Use require('express') to import Express. Then call express() to create the app. Use app.get('/error', ...) to create the route that throws an error.

2

Add PORT variable

Create a constant variable called PORT and set it to 3000.

Node.js

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

app.get('/error', (req, res, next) => {
    throw new Error('Something went wrong!');
});

// Create PORT variable set to 3000
// Your code here

Hint

Use const PORT = 3000; to create the port variable.

3

Create centralized error handler middleware

Add an error handling middleware function to app with four parameters: err, req, res, next. Inside it, send a JSON response with status set to 500 and message set to err.message.

Node.js

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

app.get('/error', (req, res, next) => {
    throw new Error('Something went wrong!');
});

const PORT = 3000;

// Add error handling middleware below
// Your code here

Hint

Use app.use with four parameters to create error middleware. Use res.status(500).json(...) to send the error response.

4

Start the server listening on PORT

Call app.listen with PORT and a callback function that does nothing (empty arrow function).

Node.js

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

app.get('/error', (req, res, next) => {
    throw new Error('Something went wrong!');
});

const PORT = 3000;

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

// Start server listening on PORT
// Your code here

Hint

Use app.listen(PORT, () => {}) to start the server.

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