How do you inject the raw HTTP request object inside a REQUEST-scoped provider in NestJS?

Q: How do you inject the raw HTTP request object inside a REQUEST-scoped provider in NestJS?

import { Injectable, Inject, Scope } from '@nestjs/common'; import { REQUEST } from '@nestjs/core'; import { Request } from 'express'; @Injectable({ scope: Scope.REQUEST }) export class AuditService { constructor(@Inject(REQUEST) private readonly request: Request) {} getCurrentUser() { return this.request.user; // set by an upstream auth guard } getClientIp(): string { return this.request.ip; } } HTTP — use REQUEST token from @nestjs/core; resolves to the Express or Fastify request object. GraphQL — use CONTEXT token from @nestjs/graphql; resolves to the GraphQL execution context. Microservices — REQUEST token resolves to the incoming message payload object. WebSockets — REQUEST token resolves to the Socket client instance.

Difficulty: 5/10

Request-scoped providers, Dependency injection, NestJS request lifecycle

Use the REQUEST token exported from @nestjs/core along with @Inject(). The provider must be decorated with scope: Scope.REQUEST. For GraphQL contexts use the CONTEXT token from @nestjs/graphql instead.

Injecting the raw HTTP request

Context tokens by transport:

1
HTTP — use REQUEST token from @nestjs/core; resolves to the Express or Fastify request object.
2
GraphQL — use CONTEXT token from @nestjs/graphql; resolves to the GraphQL execution context.
3
Microservices — REQUEST token resolves to the incoming message payload object.
4
WebSockets — REQUEST token resolves to the Socket client instance.

Scenario Questions

0-2 years experience

2-5 years experience

1We're adding a feature that reads a custom header and stores it in a per-request cache service. Walk me through how you'd inject the request object into that cache service and any pitfalls.

Follow-up Questions