Bird
Raised Fist0
Expressframework~5 mins

Centralized error handler in Express

Choose your learning style10 modes available
Introduction

A centralized error handler helps catch and manage all errors in one place. This keeps your code clean and makes debugging easier.

When you want to handle errors from many routes in one place.
When you want to send consistent error messages to users.
When you want to log errors for debugging without repeating code.
When you want to avoid crashing the server on unexpected errors.
Syntax
Express
app.use((err, req, res, next) => {
  // handle error here
  res.status(500).send('Something broke!');
});

This middleware has four parameters: err, req, res, and next. Express knows this is an error handler because it has four arguments.

Place this middleware after all other routes and middleware.

Examples
Logs the error stack to the console and sends a 500 status with a message.
Express
app.use((err, req, res, next) => {
  console.error(err.stack);
  res.status(500).send('Internal Server Error');
});
Sends different responses based on error type.
Express
app.use((err, req, res, next) => {
  if (err.type === 'database') {
    res.status(503).send('Database error');
  } else {
    res.status(500).send('Server error');
  }
});
Sample Program

This Express app throws an error on the home route. The centralized error handler catches it, logs the message, and sends a friendly error response.

Express
import express from 'express';
const app = express();

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

// Centralized error handler
app.use((err, req, res, next) => {
  console.error('Error caught:', err.message);
  res.status(500).send('Something went wrong!');
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});
OutputSuccess
Important Notes

Always place the error handler after all other middleware and routes.

Use next(err) in your routes to pass errors to this handler.

Customize error responses for better user experience.

Summary

Centralized error handlers catch all errors in one place.

They keep your code clean and consistent.

Place them last in your middleware stack.

Practice

(1/5)
1. What is the main purpose of a centralized error handler in an Express app?
easy
A. To serve static files efficiently
B. To speed up the server response time
C. To catch and handle all errors in one place
D. To manage user sessions

Solution

  1. Step 1: Understand error handling in Express

    Express allows middleware to catch errors and handle them centrally.
  2. Step 2: Identify the role of centralized error handler

    It collects all errors from routes and middleware to respond consistently.
  3. Final Answer:

    To catch and handle all errors in one place -> Option C
  4. Quick Check:

    Centralized error handler = catch all errors [OK]
Hint: Centralized error handler catches errors globally, not locally [OK]
Common Mistakes:
  • Thinking it improves server speed
  • Confusing with static file serving
  • Mixing with session management
2. Which of the following is the correct way to define a centralized error handler middleware in Express?
easy
A. app.use((req, res) => { res.status(500).send('Error'); });
B. app.use((err, req, res, next) => { res.status(500).send(err.message); });
C. app.get('/error', (err, req, res) => { res.send('Error'); });
D. app.use((req, res, next) => { res.send('Error'); });

Solution

  1. Step 1: Recall Express error handler signature

    Error handlers have four parameters: (err, req, res, next).
  2. Step 2: Match the correct middleware signature

    app.use((err, req, res, next) => { res.status(500).send(err.message); }); uses all four parameters correctly and sends error message.
  3. Final Answer:

    app.use((err, req, res, next) => { res.status(500).send(err.message); }); -> Option B
  4. Quick Check:

    Error handler middleware needs 4 params [OK]
Hint: Error handler middleware always has 4 parameters (err, req, res, next) [OK]
Common Mistakes:
  • Using only 3 parameters in error handler
  • Defining error handler as route handler
  • Missing the 'err' parameter
3. Given this Express code snippet, what will be the response if an error occurs in the route?
app.get('/test', (req, res, next) => {
  next(new Error('Oops!'));
});

app.use((err, req, res, next) => {
  res.status(500).send('Error caught: ' + err.message);
});
medium
A. Status 500 with body 'Error caught: Oops!'
B. Status 200 with body 'Oops!'
C. Status 404 with body 'Not Found'
D. No response, server crashes

Solution

  1. Step 1: Understand error propagation in route

    The route calls next() with an Error object, triggering error middleware.
  2. Step 2: Check error handler response

    The error handler sends status 500 and message including error text.
  3. Final Answer:

    Status 500 with body 'Error caught: Oops!' -> Option A
  4. Quick Check:

    Error passed to handler = 500 response with message [OK]
Hint: next(error) triggers centralized error handler with status 500 [OK]
Common Mistakes:
  • Expecting status 200 instead of 500
  • Thinking error handler is skipped
  • Assuming server crashes on error
4. Identify the error in this Express app setup for centralized error handling:
app.use((req, res, next) => {
  throw new Error('Fail');
});

app.use((req, res, next) => {
  res.status(500).send('Error occurred');
});
medium
A. Error handler middleware missing 'err' parameter
B. Throwing error inside middleware is not allowed
C. Error handler middleware should be placed before routes
D. Middleware order is correct, no error

Solution

  1. Step 1: Check error handler signature

    Error handlers must have 4 parameters: (err, req, res, next).
  2. Step 2: Analyze given error handler

    The second middleware has only (req, res, next), so it won't catch errors.
  3. Final Answer:

    Error handler middleware missing 'err' parameter -> Option A
  4. Quick Check:

    Error handler needs 4 params to catch errors [OK]
Hint: Error handler must have 4 parameters to work [OK]
Common Mistakes:
  • Forgetting the 'err' parameter in error handler
  • Placing error handler before routes
  • Thinking throwing error is disallowed
5. You want to create a centralized error handler that logs errors and sends a JSON response with status code and message. Which code snippet correctly implements this?
hard
A. app.use((req, res, next) => { console.error('Error'); res.json({ error: 'Unknown' }); });
B. app.use((err, req, res, next) => { res.send('Error occurred'); });
C. app.use((err, req, res) => { res.status(500).send('Error'); });
D. app.use((err, req, res, next) => { console.error(err); res.status(err.status || 500).json({ error: err.message }); });

Solution

  1. Step 1: Confirm error handler signature and logging

    app.use((err, req, res, next) => { console.error(err); res.status(err.status || 500).json({ error: err.message }); }); uses (err, req, res, next) and logs error with console.error.
  2. Step 2: Check response format and status code

    app.use((err, req, res, next) => { console.error(err); res.status(err.status || 500).json({ error: err.message }); }); sends JSON with error message and status code from error or 500.
  3. Final Answer:

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

    Proper error handler logs and sends JSON with status [OK]
Hint: Error handler needs 4 params, logs error, sends JSON with status [OK]
Common Mistakes:
  • Missing 'next' parameter in error handler
  • Not logging the error
  • Sending plain text instead of JSON
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard