Why middleware processes requests before handlers in NestJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does middleware run before route handlers in NestJS?

In NestJS, middleware functions run before route handlers. Why is this order important?

A Middleware runs first to modify or check the request before the handler uses it.

B Middleware runs first to send the response directly without calling handlers.

C Middleware runs after handlers to clean up resources.

D Middleware runs randomly before or after handlers depending on configuration.

💡 Hint

Think about what middleware can do with the request before the main code runs.

Middleware runs before handlers so it can inspect, modify, or validate the request. This ensures handlers get the right data or that unauthorized requests are blocked early.

❓ component_behavior

intermediate

What happens if middleware modifies the request object?

Consider this NestJS middleware that adds a property to the request object. What will the route handler see?

NestJS

export function addUserId(req, res, next) {
  req.userId = 42;
  next();
}

// Route handler
@Get('profile')
getProfile(@Req() req) {
  return req.userId;
}

A The handler receives req.userId as 42.

B The handler throws an error because userId is not defined.

C The handler receives req.userId as undefined.

D The middleware blocks the request and handler is not called.

💡 Hint

Middleware can add properties to the request object that handlers can use.

Middleware runs first and can add or change properties on the request object. The handler then accesses these properties as part of the same request.

❓ lifecycle

advanced

Order of middleware and handlers in NestJS request lifecycle

Which sequence correctly shows the order of execution when a request comes in a NestJS app with middleware and a route handler?

A 1,2,4,3

B 2,1,4,3

C 1,4,2,3

D 4,1,2,3

💡 Hint

Middleware runs first and can modify request or response before handler runs.

Middleware runs first (1), can modify request or response (4), then the route handler runs (2), and finally the response is sent (3).

📝 Syntax

advanced

Identify the correct middleware usage in NestJS

Which option correctly applies middleware to a route in NestJS?

A app.route('/route').use(middlewareFunction);

B app.use('/route', middlewareFunction);

C app.middleware('/route', middlewareFunction);

D app.applyMiddleware(middlewareFunction).forRoute('/route');

💡 Hint

Check the official NestJS way to apply middleware in main.ts or module.

In NestJS, middleware is applied using app.use(path, middleware). Other options are invalid methods.

🔧 Debug

expert

Why does this middleware not run before the handler?

Given this NestJS setup, why does the middleware not run before the route handler?

NestJS

export class AppModule implements NestModule {
  configure(consumer: MiddlewareConsumer) {
    consumer
      .apply(loggingMiddleware)
      .forRoutes('users');
  }
}

@Get('/users')
getUsers() {
  return ['Alice', 'Bob'];
}

A Middleware runs after handlers by default in NestJS.

B Middleware must be applied globally in main.ts to run before handlers.

C Middleware is not registered because configure method is missing @Injectable decorator.

D Middleware path 'users' does not match route '/users' because it lacks a leading slash.

💡 Hint

Check how paths are matched in middleware configuration.

Middleware paths must match routes exactly including the leading slash. 'users' does not match '/users', so middleware is skipped.