nestjs-patterns

Topics in the source

• NestJS Development Patterns
• When to Activate
• Project Structure
• Bootstrap and Global Validation
• Modules, Controllers, and Providers
• DTOs and Validation
• Auth, Guards, and Request Context
• Exception Filters and Error Shape

Production-grade NestJS patterns for modular TypeScript backends. Building NestJS APIs or services Structuring modules, controllers, and providers Adding DTO validation, guards, interceptors, or exception filters Configuring environment-aware settings and database integrations Testing NestJS units or HTTP endpoints Keep domain code inside feature modules. Put cross-cutting filters, decorators, guards, and interceptors in common/. Keep DTOs close to the module that owns them. Always enable whitelist and forbidNonWhitelisted on public APIs. Prefer one global validation pipe instead of repeating validation config per route. Controllers should stay thin: parse HTTP input, call a provider, return response DTOs. Put business logic in injectable services, not controllers. Export only the providers other modules genuinely need. Validate every request DTO with class-validator. Use dedicated response DTOs or serializers instead of returning ORM entities directly. Avoid leaking internal fields such as password hashes, tokens, or audit columns. Keep auth strategies and guards module-local unless they are truly shared. Encode coarse access rules in guards, then do resource-specific authorizatio

This is an excerpt. Refer to the complete source and its current requirements.