nest-conventions

To prevent architectural drift in a NestJS backend, enforce a module-per-feature layout where one feature equals a dedicated module. This standardizes dependency injection wiring, global config patterns, and lifecycle hooks, keeping the codebase maintainable as it scales.

The correct way to wire dependency injection in NestJS involves using constructor injection, managing scopes, and applying custom tokens. For lifecycle usage, implement OnModuleInit and OnApplicationShutdown interfaces to ensure reliable application startup and graceful shutdown processes.

Set up ConfigModule in a NestJS backend by applying proper initialization patterns at the root AppModule level. Combine this with ValidationPipe usage and proper exception filters to validate inputs and handle errors uniformly across all feature modules.

No specific external dependencies or components are required to apply these NestJS module conventions. The approach relies entirely on standard NestJS structural patterns, built-in lifecycle interfaces, and native dependency injection features to enforce architectural consistency.

Use OnModuleInit and OnApplicationShutdown lifecycle hooks in NestJS when you need reliable startup initialization and graceful shutdown processes. Applying these hooks ensures your feature modules properly manage resources during application lifecycle transitions.