Can a pipe be asynchronous in NestJS and how do you implement one?

Q: Can a pipe be asynchronous in NestJS and how do you implement one?

@Injectable() export class UserExistsPipe implements PipeTransform { constructor(private usersService: UsersService) {} async transform(id: string): Promise { const parsed = parseInt(id, 10); if (isNaN(parsed)) throw new BadRequestException('id must be a number'); const user = await this.usersService.findOne(parsed); if (!user) throw new NotFoundException(`User #${parsed} not found`); return user; // handler receives the full User, not just the id string } } // Handler receives the resolved User — no findOne call needed inside @Get(':id') findOne(@Param('id', UserExistsPipe) user: User) { return user; } Return Promise from transform() — NestJS awaits it before calling the handler. Async pipes that inject services must use the DI container — register as @Injectable() provider. Pass the pipe as a class reference so NestJS resolves its dependencies: @Param('id', UserExistsPipe). Using new UserExistsPipe() bypasses DI — the injected service will be undefined. Async pipes increase request latency by the time of the awaited operation — use wisely.

Difficulty: 5/10

asynchronous pipes, validation, dependency injection

Yes. The transform() method can return a Promise and NestJS automatically awaits it before injecting the value into the handler. Async pipes are used for database-backed validation — for example, checking that an entity exists and returning it directly so the handler receives the full object instead of a raw ID string.

Async pipe that resolves a User from the database

Async pipe rules and considerations:

1
Return Promise<T> from transform() — NestJS awaits it before calling the handler.
2
Async pipes that inject services must use the DI container — register as @Injectable() provider.
3
Pass the pipe as a class reference so NestJS resolves its dependencies: @Param('id', UserExistsPipe).
4
Using new UserExistsPipe() bypasses DI — the injected service will be undefined.
5
Async pipes increase request latency by the time of the awaited operation — use wisely.

Scenario Questions

0-2 years experience

Follow-up Questions