Middleware ordering and its importance in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when middleware order is changed?

Consider this Express app code snippet. What will be the response when a GET request is made to /test?

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

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

app.get('/test', (req, res, next) => {
  res.send('Hello from /test');
  next();
});

app.use((req, res) => {
  res.send('Fallback middleware');
});

app.listen(3000);

Now, if we move the fallback middleware app.use((req, res) => {...}) above the app.get('/test', ...) route, what will happen?

Express

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

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

// Fallback middleware moved here
app.use((req, res) => {
  res.send('Fallback middleware');
});

app.get('/test', (req, res, next) => {
  res.send('Hello from /test');
  next();
});

app.listen(3000);

A The response will be empty because next() is called after res.send() in the route.

B The response will be 'Hello from /test' because route handlers always run before middleware.

C The server will crash with an error because middleware order is invalid.

D The response will be 'Fallback middleware' for GET /test because fallback middleware runs before the route handler.

💡 Hint

Think about how Express processes middleware and routes in the order they are added.

Express runs middleware and routes in the order they are registered. If the fallback middleware is placed before the route, it will catch the request and send a response first. The route handler will never run because the response is already sent.

❓ lifecycle

intermediate

Which middleware runs first in this Express app?

Given the following Express app setup, which middleware function will run first when a request is made to /api/data?

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

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

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

app.get('/api/data', (req, res) => {
  res.send('Data response');
});

app.listen(3000);

A 'General middleware' runs first because it is registered before the API middleware.

B 'API middleware' runs first because it matches the /api path prefix.

C Both middlewares run simultaneously.

D Only the route handler runs; middleware is skipped.

💡 Hint

Remember that middleware with path prefixes only run if the request path matches.

Middleware registered with a path prefix like '/api' only runs for matching routes. Since the request is to '/api/data', the '/api' middleware runs first. Then the general middleware runs because it applies to all paths.

🔧 Debug

advanced

Why does this Express app hang without responding?

Look at this Express app code. Why does it hang and never send a response?

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

app.use((req, res, next) => {
  console.log('Middleware 1');
  // Missing next() call
});

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

app.listen(3000);

A Middleware 1 does not call next(), so the request never reaches the route handler.

B The app.listen() call is missing a callback, causing the hang.

C Express requires res.end() to be called explicitly in middleware.

D The route handler is missing a next() call, causing the hang.

💡 Hint

Think about how Express moves from one middleware to the next.

Middleware functions must call next() to pass control to the next middleware or route. Since Middleware 1 does not call next() or send a response, the request hangs.

📝 Syntax

advanced

What error does this middleware code produce?

Examine this Express middleware code snippet. What error will it cause?

app.use((req, res, next) => {
  if(req.method === 'GET')
    next();
  else
    res.send('Only GET allowed');
    next();
});

A Error: Cannot set headers after they are sent to the client

B SyntaxError: Unexpected token else

C No error; middleware works correctly

D TypeError: next is not a function

💡 Hint

Look carefully at the indentation and flow of next() calls.

The else block sends a response but then next() is called again outside the else block, causing Express to try to continue after response is sent, leading to 'Cannot set headers after they are sent' error.

🧠 Conceptual

expert

Why is middleware ordering critical in Express apps?

Which of the following best explains why the order of middleware matters in Express?

A Middleware order only matters if you use error-handling middleware.

B Middleware order only affects performance but not the correctness of responses.

C Middleware order determines the sequence of request processing; incorrect order can block routes or cause unexpected responses.

D Middleware order is irrelevant because Express runs all middleware in parallel.

💡 Hint

Think about how Express passes requests through middleware and routes.

Express processes middleware and routes in the order they are registered. If middleware that sends a response runs before a route, the route never executes. Thus, order controls flow and response behavior.