What are the two ways to register a global pipe in NestJS and what is the difference?

Q: What are the two ways to register a global pipe in NestJS and what is the difference?

// Option 1 — app.useGlobalPipes() — outside DI, no injection support async function bootstrap() { const app = await NestFactory.create(AppModule); app.useGlobalPipes(new ValidationPipe({ whitelist: true })); await app.listen(3000); } // Option 2 — APP_PIPE token — inside DI, full injection support (preferred) @Module({ providers: [ { provide: APP_PIPE, useClass: ValidationPipe, }, ], }) export class AppModule {} // Option 2 with factory — options from ConfigService @Module({ providers: [ { provide: APP_PIPE, useFactory: (config: ConfigService) => new ValidationPipe({ whitelist: config.get('WHITELIST') === 'true' }), inject: [ConfigService], }, ], }) export class AppModule {} app.useGlobalPipes() — simple, works well for stateless pipes with no dependencies. APP_PIPE token — pipe is managed by the DI container and can inject other providers. useFactory with APP_PIPE allows ValidationPipe options to be read from ConfigService. APP_PIPE is defined in @nestjs/core — import it from there, not from @nestjs/common. Multiple APP_PIPE providers can be registered — they all run globally in registration order.

Difficulty: 5/10

global pipes, dependency injection, validation

app.useGlobalPipes() registers the pipe outside the DI container — it cannot inject services. The APP_PIPE token registers the pipe inside the DI container — it supports full constructor injection and is the preferred approach for any pipe with dependencies or options loaded from environment config.

Global pipe registration — both methods

Choosing between the two methods:

1
app.useGlobalPipes() — simple, works well for stateless pipes with no dependencies.
2
APP_PIPE token — pipe is managed by the DI container and can inject other providers.

What are the two ways to register a global pipe in NestJS and what is the difference?

Difficulty: 5/10

global pipes, dependency injection, validation

app.useGlobalPipes() registers the pipe outside the DI container — it cannot inject services. The APP_PIPE token registers the pipe inside the DI container — it supports full constructor injection and is the preferred approach for any pipe with dependencies or options loaded from environment config.

Global pipe registration — both methods

Choosing between the two methods:

1
app.useGlobalPipes() — simple, works well for stateless pipes with no dependencies.
2
APP_PIPE token — pipe is managed by the DI container and can inject other providers.

What are the two ways to register a global pipe in NestJS and what is the difference?

What are the two ways to register a global pipe in NestJS and what is the difference?

Scenario Questions

Follow-up Questions