Why middleware is fundamental in Node.js

Introduction

Middleware helps organize code that runs between receiving a request and sending a response. It makes your app easier to build and maintain.

You want to check if a user is logged in before showing a page.

You need to log every request made to your server.

You want to handle errors in one place instead of everywhere.

You want to add headers or modify requests and responses.

You want to serve static files like images or stylesheets.

Syntax

Node.js

function middlewareFunction(req, res, next) {
  // Do something with req or res
  next(); // Pass control to the next middleware
}

Middleware functions take three arguments: request, response, and next.

Calling next() moves to the next middleware or route handler.

Examples

This middleware logs the URL of every request.

Node.js

app.use(function(req, res, next) {
  console.log('Request URL:', req.url);
  next();
});

This middleware checks if a user is logged in before continuing.

Node.js

app.use(function(req, res, next) {
  if (!req.user) {
    res.status(401).send('Not logged in');
  } else {
    next();
  }
});

Sample Program

This example shows two middleware functions: one logs requests, the other adds a header. Then a route sends a welcome message.

Node.js

import express from 'express';

const app = express();

// Middleware to log request method and URL
app.use((req, res, next) => {
  console.log(`${req.method} ${req.url}`);
  next();
});

// Middleware to add a custom header
app.use((req, res, next) => {
  res.setHeader('X-Custom-Header', 'HelloMiddleware');
  next();
});

// Route handler
app.get('/', (req, res) => {
  res.send('Welcome to middleware demo!');
});

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

Important Notes

Always call next() unless you end the response to avoid hanging requests.

Middleware runs in the order you add it, so order matters.

Summary

Middleware runs code between request and response.

It helps keep your app organized and reusable.

Use middleware for logging, authentication, error handling, and more.

Practice

1. What is the main role of middleware in a Node.js application?

easy

A. To run code between receiving a request and sending a response

B. To directly send HTML pages to the client

C. To store data permanently in a database

D. To compile JavaScript code into machine code

Solution

1. Step 1: Understand middleware position in request flow

   Middleware functions run after a request is received but before the response is sent back.

2. Step 2: Identify middleware purpose

   Middleware is used to process or modify requests and responses, like logging or authentication, not to send pages or store data directly.

3. Final Answer:

   To run code between receiving a request and sending a response -> Option A

4. Quick Check:

   Middleware = code between request and response [OK]

Hint: Middleware runs between request and response [OK]

Common Mistakes:

• Thinking middleware sends the final response directly
• Confusing middleware with database operations
• Assuming middleware compiles code

2. Which of the following is the correct way to define a middleware function in Express.js?

easy

A. app.use((req, res, next) => { console.log('Middleware'); next(); });

B. app.get((req, res) => { console.log('Middleware'); });

C. app.listen((req, res, next) => { next(); });

D. app.middleware((req, res, next) => { next(); });

Solution

1. Step 1: Recall Express middleware syntax

   Middleware is added using app.use() with a function that takes req, res, and next parameters.

2. Step 2: Check each option

   app.use((req, res, next) => { console.log('Middleware'); next(); }); uses app.use() correctly and calls next() to pass control. Others use wrong methods or miss next().

3. Final Answer:

   app.use((req, res, next) => { console.log('Middleware'); next(); }); -> Option A

4. Quick Check:

   Middleware uses app.use() and next() [OK]

Hint: Middleware uses app.use() with next() call [OK]

Common Mistakes:

• Using app.get() instead of app.use() for middleware
• Forgetting to call next() inside middleware
• Using non-existent app.middleware() method

3. Consider this Express middleware code snippet:

app.use((req, res, next) => { console.log('First'); next(); });
app.use((req, res, next) => { console.log('Second'); res.send('Done'); });
app.use((req, res, next) => { console.log('Third'); next(); });

What will be printed in the console when a request is made?

medium

A. First\nSecond\nThird

B. First\nSecond

C. Second\nThird

D. First only

Solution

1. Step 1: Trace middleware execution order

   Middleware runs in order. First logs 'First' and calls next(), so second runs next.

2. Step 2: Check response behavior in second middleware

   Second logs 'Second' and sends response with res.send('Done'), ending the request cycle. Third middleware is not called.

3. Final Answer:

   First\nSecond -> Option B

4. Quick Check:

   Middleware stops after res.send() [OK]

Hint: Middleware stops after res.send() without next() [OK]

Common Mistakes:

• Assuming all middleware always run
• Ignoring that res.send() ends response
• Thinking next() is called automatically after res.send()

4. You wrote this middleware but your app crashes with an error:

app.use((req, res) => { console.log('Logging request'); });

What is the problem?

medium

A. Middleware must send a response directly

B. Middleware cannot use console.log

C. Middleware must have three parameters: req, res, and next

D. Middleware should be defined after app.listen()

Solution

1. Step 1: Check middleware function parameters

   Express middleware needs three parameters: req, res, and next to pass control to next middleware.

2. Step 2: Identify missing next parameter

   The given middleware only has req and res, so it cannot call next(), causing the app to hang or crash.

3. Final Answer:

   Middleware must have three parameters: req, res, and next -> Option C

4. Quick Check:

   Middleware needs next parameter [OK]

Hint: Middleware needs (req, res, next) parameters [OK]

Common Mistakes:

• Omitting the next parameter
• Thinking console.log causes errors
• Believing middleware must always send response

5. You want to add middleware that logs request method and URL, then checks if user is authenticated before continuing. Which code correctly combines these tasks?

hard

A. app.use((req, res, next) => { console.log(req.method, req.url); next(); res.send('Unauthorized'); });

B. app.use((req, res) => { console.log(req.method, req.url); next(); if (!req.user) res.send('Unauthorized'); });

C. app.use((req, res, next) => { if (!req.user) next(); console.log(req.method, req.url); next(); });

D. app.use((req, res, next) => { console.log(req.method, req.url); if (!req.user) return res.status(401).send('Unauthorized'); next(); });

Solution

1. Step 1: Log request method and URL first

   app.use((req, res, next) => { console.log(req.method, req.url); if (!req.user) return res.status(401).send('Unauthorized'); next(); }); logs method and URL immediately, which is correct for logging middleware.

2. Step 2: Check authentication before calling next()

   app.use((req, res, next) => { console.log(req.method, req.url); if (!req.user) return res.status(401).send('Unauthorized'); next(); }); checks if req.user exists; if not, it sends 401 response and stops. Otherwise, it calls next() to continue.

3. Step 3: Verify other options

   The other options misuse next() or res.send(), causing incorrect flow or multiple calls.

4. Final Answer:

   app.use((req, res, next) => { console.log(req.method, req.url); if (!req.user) return res.status(401).send('Unauthorized'); next(); }); -> Option D

5. Quick Check:

   Log then check auth, call next() only if authorized [OK]

Hint: Log first, then check auth, call next() only if authorized [OK]

Common Mistakes:

• Calling next() after sending response
• Not stopping middleware on unauthorized access
• Logging after next() causing missed logs