nestjs-best-practices

Critical NestJS production patterns include enforcing constructor injection, avoiding circular dependencies, and centralizing exception handling. These architecture and dependency injection guardrails ensure modules remain testable, maintainable, and uniformly structured across multiple microservices.

Audit NestJS microservices by validating input, implementing caching strategies, and enforcing API versioning. Reviewing code against documented rule files across API gateway, auth, and finance services ensures uniform security and performance standards before production deployment.

Standardize testing and DevOps workflows by compiling an AGENTS.md master document from priority-ordered rule categories. This reference-ready workflow aligns reviewers and authors on deployment hygiene and testing expectations across gateway, club, inventory, and booking services.

Yes, the best practices guide applies to both monolithic and microservices NestJS architectures. It audits API gateway, admin gateway, auth, club, inventory, booking, and finance services, enforcing uniform production standards whenever NestJS code is written, reviewed, or refactored.

Avoid circular dependencies in NestJS by strictly enforcing constructor injection and organizing modules by bounded context. The guide's critical architecture and dependency injection guardrails provide actionable directives to triage focus areas and maintain structured code quality.

Centralized exception handling should not be bypassed when custom error trapping is needed, as the guide mandates centralizing it to maintain uniform production standards. Deviating from documented rule files breaks the structured code quality expected across auth and finance services.