This program uses two middleware functions. The first logs the request method and URL. The second adds a message to the request. The route then sends that message back to the browser.
Always call next() unless you send a response to avoid hanging requests.
Middleware runs in the order you add it with app.use().
Error-handling middleware has four arguments: (err, req, res, next).
Summary
Middleware lets you run code on requests before reaching routes.
Use next() to pass control to the next middleware.
Order matters: middleware runs in the order you add it.
Practice
(1/5)
1. What is the main purpose of middleware in a Node.js Express app?
easy
A. To style the HTML pages
B. To directly send responses to the client without routes
C. To define database schemas
D. To run code on requests before they reach the route handlers
Solution
Step 1: Understand middleware role and compare options
Middleware functions run before route handlers to process requests. Only To run code on requests before they reach the route handlers describes middleware's role correctly; others describe unrelated tasks.
Final Answer:
To run code on requests before they reach the route handlers -> Option D
Quick Check:
Middleware = Pre-route code [OK]
Hint: Middleware runs before routes to handle requests [OK]
Common Mistakes:
Thinking middleware sends responses directly
Confusing middleware with database logic
Assuming middleware styles pages
2. Which of the following is the correct way to define a middleware function in Express?
easy
A. app.get((req, res) => { console.log('Middleware'); });
B. app.use((req, res, next) => { console.log('Middleware'); next(); });
C. app.middleware((req, res, next) => { next(); });
D. app.route('/').middleware((req, res) => { next(); });
Solution
Step 1: Recall Express middleware syntax and check options
Middleware uses app.use() with (req, res, next) parameters. Only app.use((req, res, next) => { console.log('Middleware'); next(); }); uses app.use() and calls next(), which is correct middleware syntax.
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
Step 1: Understand middleware execution order and route handler
Middleware runs in the order added: first prints 'First', then calls next(), second prints 'Second'. After middleware, route handler sends response but does not print to console.
Final Answer:
First\nSecond -> Option A
Quick Check:
Middleware order = console logs order [OK]
Hint: Middleware logs appear in order added before route runs [OK]
D. It uses wrong parameters in middleware function
Solution
Step 1: Check middleware function and request flow effect
The middleware logs 'Start' but does not call next(), so it blocks further processing. Without next(), the route handler never runs, so the request hangs.
Final Answer:
It never calls next(), so the request hangs -> Option C
Quick Check:
Missing next() blocks request [OK]
Hint: Always call next() in middleware unless sending response [OK]
Common Mistakes:
Forgetting to call next() in middleware
Calling next() multiple times
Confusing middleware parameters
5. You want to add two middleware functions to log request time and check authentication before handling routes. Which code correctly ensures both run in order and the route handler executes after?