Middleware ordering matters in Node.js

Introduction

Middleware functions run in the order they are added. This order controls how requests are handled step-by-step.

When you want to log requests before processing them

When you need to check user authentication before allowing access

When you want to parse incoming data before using it

When you want to handle errors after all other middleware

When you want to serve static files before other routes

Syntax

Node.js

app.use(middlewareFunction1);
app.use(middlewareFunction2);
app.use(middlewareFunction3);

Middleware runs in the order you add them with app.use() or route methods.

If a middleware does not call next(), the chain stops there.

Examples

This example shows two middleware functions running one after the other.

Node.js

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

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

Here, JSON parsing middleware runs before the handler that sends back the parsed data.

Node.js

app.use(express.json());
app.use((req, res) => {
  res.send(req.body);
});

Authentication middleware runs before the route handler to protect the profile page.

Node.js

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

app.get('/profile', (req, res) => {
  res.send('User profile');
});

Sample Program

This program shows two middleware functions running in order before the route handler. The first logs the request, the second adds a header, then the route sends a response.

Node.js

import express from 'express';

const app = express();

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

// Middleware 2: Adds a custom header
app.use((req, res, next) => {
  res.setHeader('X-Custom-Header', 'Hello');
  next();
});

// Route handler
app.get('/', (req, res) => {
  res.send('Home page');
});

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

Important Notes

If middleware order is wrong, requests might not be handled as expected.

Always call next() unless you send a response to avoid hanging requests.

Put error-handling middleware last to catch errors from earlier middleware.

Summary

Middleware runs in the order you add it.

Order affects how requests are processed and responses are sent.

Always plan middleware order carefully for correct app behavior.

Practice

1. In a Node.js Express app, why does the order of middleware matter?

easy

A. Because middleware order controls the file system permissions

B. Because middleware order changes the port the server listens on

C. Because middleware order determines the database connection string

D. Because middleware runs in the order it is added, affecting request handling

Solution

1. Step 1: Understand middleware execution order

   Middleware functions in Express run in the sequence they are added to the app. This order controls how requests are processed.

2. Step 2: Recognize impact on request handling

   If middleware is out of order, some requests might not be handled correctly or responses might be sent too early.

3. Final Answer:

   Because middleware runs in the order it is added, affecting request handling -> Option D

4. Quick Check:

   Middleware order affects request flow = D [OK]

Hint: Middleware runs top to bottom in code order [OK]

Common Mistakes:

• Thinking middleware order affects server port
• Confusing middleware order with database config
• Assuming middleware order controls file permissions

2. Which of the following is the correct way to add middleware in Express to ensure it runs before route handlers?

easy

A. app.use(middlewareFunction); app.get('/route', handler);

B. app.get('/route', handler); app.use(middlewareFunction);

C. app.listen(3000); app.use(middlewareFunction);

D. app.get('/route', middlewareFunction, handler); app.use();

Solution

1. Step 1: Identify middleware placement

   Middleware should be added before route handlers to process requests first.

2. Step 2: Check code order

   app.use(middlewareFunction); app.get('/route', handler); adds middleware with app.use before defining the route, ensuring middleware runs first.

3. Final Answer:

   app.use(middlewareFunction); app.get('/route', handler); -> Option A

4. Quick Check:

   Middleware before routes = C [OK]

Hint: Add middleware before routes to run first [OK]

Common Mistakes:

• Adding middleware after routes so it never runs
• Calling app.listen before middleware
• Incorrect middleware syntax in routes

3. Consider this Express code snippet:

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

What will be printed in the console when a GET request is made to '/'?

medium

A. First\nSecond

B. Second\nFirst

C. Done

D. No output

Solution

1. Step 1: Trace middleware execution order

   The first middleware logs 'First' then calls next(), so the second middleware runs next.

2. Step 2: Trace second middleware and route handler

   The second middleware logs 'Second' then calls next(), leading to the route handler sending 'Done'.

3. Final Answer:

   First\nSecond -> Option A

4. Quick Check:

   Middleware logs in order added = B [OK]

Hint: Middleware logs appear in code order [OK]

Common Mistakes:

• Assuming logs appear reversed
• Expecting 'Done' in console instead of response
• Thinking middleware skips if next() is called

4. You have this Express code:

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

What is the problem with this middleware order?

medium

A. Middleware 1 does not call next(), so Middleware 2 runs twice

B. Middleware 2 will never run because next() is missing

C. Calling next() after res.send() causes an error or unexpected behavior

D. There is no problem; this order is correct

Solution

1. Step 1: Understand res.send() effect

   Calling res.send() sends the response and ends the request cycle.

2. Step 2: Analyze calling next() after res.send()

   Calling next() after res.send() can cause errors or unexpected behavior because the response is already sent.

3. Final Answer:

   Calling next() after res.send() causes an error or unexpected behavior -> Option C

4. Quick Check:

   Don't call next() after res.send() = A [OK]

Hint: Never call next() after sending response [OK]

Common Mistakes:

• Thinking next() is optional after res.send()
• Assuming middleware 2 runs normally
• Ignoring that response ends request

5. You want to add a logging middleware that logs every request, an authentication middleware that blocks unauthorized users, and a route handler. Which order ensures unauthorized requests are blocked before routes run, but all requests are logged?

hard

A. Authentication middleware, Logging middleware, Route handler

B. Logging middleware, Authentication middleware, Route handler

C. Route handler, Logging middleware, Authentication middleware

D. Route handler, Authentication middleware, Logging middleware

Solution

1. Step 1: Determine middleware purpose order

   Logging should happen for all requests first, so it must be first.

2. Step 2: Place authentication before route handler

   Authentication must run before routes to block unauthorized access.

3. Step 3: Confirm route handler last

   Route handler runs last after middleware passes.

4. Final Answer:

   Logging middleware, Authentication middleware, Route handler -> Option B

5. Quick Check:

   Log first, then auth, then route = A [OK]

Hint: Log first, authenticate second, handle route last [OK]

Common Mistakes:

• Putting authentication before logging misses some logs
• Running route before middleware breaks flow
• Assuming order does not affect blocking unauthorized users