NestJS

NestJS

Overview

A brief summary of what the skill does and its core philosophy.

When to Use

Context for when this skill is applicable.

Rules & Patterns

NestJS — Best Practices

Module Architecture

• One module per domain — UsersModule, AuthModule, OrdersModule
• Feature modules — encapsulate related controllers, services, repositories
• Shared module — for cross-cutting concerns (logging, config, utils)
• Core module — singleton services (database, auth guards)

src/
├── modules/
│   ├── users/
│   │   ├── users.module.ts
│   │   ├── users.controller.ts
│   │   ├── users.service.ts
│   │   ├── users.repository.ts
│   │   ├── dto/
│   │   │   ├── create-user.dto.ts
│   │   │   └── update-user.dto.ts
│   │   ├── entities/
│   │   │   └── user.entity.ts
│   │   └── users.spec.ts
│   └── auth/
├── shared/
│   ├── guards/
│   ├── interceptors/
│   ├── pipes/
│   └── filters/
├── config/
└── app.module.ts

Dependency Injection

@Injectable()
export class UsersService {
  constructor(
    @InjectRepository(User) private readonly usersRepo: Repository<User>,
    private readonly configService: ConfigService,
  ) {}
}

• Prefer constructor injection
• Use custom providers for complex setup
• Scope: default is Singleton, use REQUEST scope only when needed

DTOs and Validation

import { IsEmail, IsString, MinLength } from 'class-validator';

export class CreateUserDto {
  @IsEmail()
  email: string;

  @IsString()
  @MinLength(2)
  name: string;
}

• Always use DTOs for request validation
• Use ValidationPipe globally
• Separate Create/Update/Response DTOs

Guards, Interceptors, Pipes

Type	Purpose
Guards	Authentication, authorization
Interceptors	Logging, transformation, caching
Pipes	Validation, transformation
Filters	Exception handling

Execution order: Guards → Interceptors → Pipes → Handler → Interceptors → Filters