Middleware ordering matters in Node.js - Step-by-Step Execution

Concept Flow - Middleware ordering matters

Request comes in

↓

Middleware 1 runs

↓

Middleware 2 runs

↓

Middleware 3 runs

↓

Response sent

Middleware functions run in the order they are added. Each must call next() to pass control to the next middleware. If next() is skipped, later middleware won't run.

Execution Sample

Node.js

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

Three middleware functions are added; the first two run in order, but the second one does not call next(), so the chain stops and the third does not run.

Execution Table

Step	Middleware	Action	next() Called?	Console Output	Next Middleware Runs?
1	Middleware 1	Runs and logs 'First'	Yes	First	Yes
2	Middleware 2	Runs and logs 'Second'	No	Second	No
3	Middleware 3	Skipped because previous did not call next()	N/A		No
4	Response	Skipped because chain stopped at Middleware 2	N/A		N/A

💡 Middleware 2 did not call next(), so middleware 3 and response sending are skipped.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
nextCalled	false	true	false	false
consoleOutput	''	'First'	'First\nSecond'	'First\nSecond'
middlewareIndex	0	1	2	2

Key Moments - 2 Insights

Why does Middleware 3 not run even though it is defined?

Because Middleware 2 did not call next(), the chain stops there as shown in execution_table row 2 and 3.

What happens if a middleware forgets to call next()?

The request stops at that middleware and later middleware or response sending won't happen, as seen in execution_table row 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the console output after Middleware 2 runs?

A "Second"

B "First"

C "First\nSecond"

D ""

💡 Hint

Check the 'Console Output' column at Step 2 in the execution_table.

At which step does the middleware chain stop?

A After Middleware 1

B After Middleware 2

C After Middleware 3

D After response sent

💡 Hint

Look at the 'Next Middleware Runs?' column in execution_table rows 2 and 3.

If Middleware 2 called next(), what would happen?

A Middleware 3 would run next

B Middleware 1 would run again

C Response would be sent immediately

D Nothing changes

💡 Hint

Middleware chain continues only if next() is called, see concept_flow and execution_table.

Concept Snapshot

Middleware functions run in the order they are added.
Each middleware must call next() to pass control.
If next() is not called, the chain stops.
Ordering matters because earlier middleware can block later ones.
Always ensure next() is called unless ending the response.

Full Transcript

Middleware ordering matters in Node.js because each middleware function runs in the order it is added to the app. When a request comes in, the first middleware runs and must call next() to pass control to the next middleware. If a middleware does not call next(), the chain stops and later middleware do not run. In the example, Middleware 1 logs 'First' and calls next(), so Middleware 2 runs next. Middleware 2 logs 'Second' but does not call next(), so Middleware 3 and the response sending are skipped. This shows why middleware ordering and calling next() are important to control the flow of request handling.