Middleware ordering matters in Node.js - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a middleware that logs every request.

Node.js

app.use([1]);

Drag options to blanks, or click blank then click option'

AloggerMiddleware

Bexpress.json()

CerrorHandler

Drouter

Attempts:

3 left

💡 Hint

Common Mistakes

Using errorHandler instead of loggerMiddleware

Adding router before loggerMiddleware

Using express.json() which parses JSON, not logs

The loggerMiddleware logs every request. It should be added with app.use() to run on all requests.

2fill in blank

medium

Complete the code to parse JSON bodies in requests.

Node.js

app.use([1]);

Drag options to blanks, or click blank then click option'

AloggerMiddleware

BerrorHandler

Cexpress.json()

Drouter

Attempts:

3 left

💡 Hint

Common Mistakes

Using loggerMiddleware instead of express.json()

Adding errorHandler before routes

Not adding JSON parser middleware at all

express.json() is middleware that parses JSON request bodies. It should be added before routes that need to read JSON data.

3fill in blank

hard

Fix the error in middleware order to ensure errorHandler catches errors.

Node.js

app.use(router);
app.use([1]);

Drag options to blanks, or click blank then click option'

AloggerMiddleware

BerrorHandler

Cexpress.json()

Dcors()

Attempts:

3 left

💡 Hint

Common Mistakes

Adding errorHandler before router

Using loggerMiddleware as error handler

Not adding errorHandler at all

Error handling middleware must be added after all route handlers to catch errors properly.

4fill in blank

hard

Fill both blanks to add JSON parsing and routing middleware in correct order.

Node.js

app.use([1]);
app.use([2]);

Drag options to blanks, or click blank then click option'

Aexpress.json()

Brouter

CerrorHandler

DloggerMiddleware

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the order of JSON parser and router

Adding errorHandler before router

Adding loggerMiddleware after router

JSON parsing middleware must come before routing middleware so routes can access parsed data.

5fill in blank

hard

Fill all three blanks to add logging, JSON parsing, and error handling middleware in correct order.

Node.js

app.use([1]);
app.use([2]);
app.use([3]);

Drag options to blanks, or click blank then click option'

AloggerMiddleware

Bexpress.json()

CerrorHandler

Drouter

Attempts:

3 left

💡 Hint

Common Mistakes

Placing errorHandler before logger or JSON parser

Skipping loggerMiddleware

Adding router instead of errorHandler last

Logging middleware should run first, then JSON parsing, then error handling last.

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