next() function and flow control in Express

Introduction

The next() function helps move from one step to the next in Express. It controls how requests flow through different parts of your app.

When you want to pass control from one middleware to another.

When you need to handle errors by moving to error-handling middleware.

When you want to split your app logic into small, manageable pieces.

When you want to skip some middleware under certain conditions.

When you want to make sure your app responds only once per request.

Syntax

Express

function middleware(req, res, next) {
  // your code here
  next(); // pass control to next middleware
}

The next parameter is a function you call to continue the request flow.

If you don't call next() or send a response, the request will hang.

Examples

This middleware logs a message and then calls next() to continue.

Express

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

This middleware checks if the user is logged in. If not, it sends a response and stops. Otherwise, it calls next().

Express

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

This is error-handling middleware. It catches errors passed by calling next(err).

Express

app.use((err, req, res, next) => {
  console.error(err);
  res.status(500).send('Server error');
});

Sample Program

This app uses two middleware functions before the final route handler. The first logs the request method. The second checks if the query parameter name exists. If missing, it sends an error response. Otherwise, it calls next() to reach the final handler that greets the user.

Express

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

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

// Middleware 2: Checks for a query param 'name'
app.use((req, res, next) => {
  if (!req.query.name) {
    res.status(400).send('Name query param missing');
  } else {
    next();
  }
});

// Final handler: Sends greeting
app.get('/', (req, res) => {
  res.send(`Hello, ${req.query.name}!`);
});

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

Important Notes

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

Use next(err) to pass errors to error-handling middleware.

Order of middleware matters; Express runs them in the order you add them.

Summary

next() moves control to the next middleware or route.

It helps split your app into small steps that run one after another.

Calling next() or sending a response is required to finish handling a request.

Practice

1. What does the next() function do in Express middleware?

easy

A. It logs the request details to the console.

B. It passes control to the next middleware or route handler.

C. It restarts the current middleware from the beginning.

D. It ends the request and sends a response to the client.

Solution

1. Step 1: Understand middleware flow

   Express middleware functions run in sequence. Calling next() moves control to the next middleware or route.

2. Step 2: Identify next() role

   Calling next() does not send a response but passes control forward, allowing the app to continue processing.

3. Final Answer:

   It passes control to the next middleware or route handler. -> Option B

4. Quick Check:

   next() moves control forward [OK]

Hint: Remember: next() moves to next step, doesn't send response [OK]

Common Mistakes:

• Thinking next() sends a response
• Confusing next() with ending the request
• Assuming next() restarts middleware

2. Which of the following is the correct syntax to use next() in an Express middleware function?

easy

A. function(req, res, next) { res.next(); }

B. function(req, res) { next(); }

C. function(req, res, next) { next(); }

D. function(req, res, next) { next; }

Solution

1. Step 1: Check middleware parameters

   Express middleware must have three parameters: req, res, and next to use next().

2. Step 2: Verify calling next()

   The correct way to call next() is as a function with parentheses: next();

3. Final Answer:

   function(req, res, next) { next(); } -> Option C

4. Quick Check:

   Correct syntax includes next as parameter and calls next() [OK]

Hint: next() must be called as a function with parentheses [OK]

Common Mistakes:

• Omitting next parameter
• Calling next without parentheses
• Using res.next() instead of next()

3. Consider this Express middleware chain:

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

B. First\nSecond\nThird

C. Second\nThird

D. First

Solution

1. Step 1: Trace middleware execution order

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

2. Step 2: Check response and flow stop

   The second middleware logs 'Second' and sends a response with res.send('Done'). Sending a response ends the request, so the third middleware does not run.

3. Final Answer:

   First\nSecond -> Option A

4. Quick Check:

   Response sent stops flow, so third middleware skipped [OK]

Hint: Sending response stops middleware chain immediately [OK]

Common Mistakes:

• Assuming all middleware run even after response
• Thinking next() runs after res.send()
• Ignoring that res.send ends request

4. What is wrong with this Express middleware?

app.use((req, res, next) => {
  console.log('Logging request');
  // forgot to call next or send response
});

medium

A. It will cause the request to hang and never finish.

B. It will automatically call next() after logging.

C. It will send an empty response to the client.

D. It will throw a syntax error.

Solution

1. Step 1: Identify missing flow control

   The middleware logs a message but neither calls next() nor sends a response.

2. Step 2: Understand Express behavior

   Without calling next() or sending a response, Express waits indefinitely, causing the request to hang.

3. Final Answer:

   It will cause the request to hang and never finish. -> Option A

4. Quick Check:

   Missing next() or response causes hanging [OK]

Hint: Always call next() or send response to finish middleware [OK]

Common Mistakes:

• Assuming Express auto-calls next()
• Thinking console.log ends request
• Expecting default response without sending

5. You want to create middleware that checks if a user is logged in. If not logged in, it should send a 401 response. If logged in, it should continue to the next middleware. Which code correctly uses next() to achieve this?

hard

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

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

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

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

Solution

1. Step 1: Check user login condition

   If req.user is missing, the middleware should send a 401 Unauthorized response immediately.

2. Step 2: Use next() correctly

   If the user is logged in, call next() to pass control to the next middleware or route handler.

3. Final Answer:

   Middleware sends 401 if no user, else calls next() -> Option D

4. Quick Check:

   Send response before next(), or call next() to continue [OK]

Hint: Send response first if unauthorized; call next() only if authorized [OK]

Common Mistakes:

• Calling next() before sending response
• Swapping conditions for sending response
• Calling next() after sending response