nestjs-domain

What problem does it solve?

It keeps NestJS domain layers free of framework and persistence details, ensuring teams do not accidentally leak infrastructure into entities, value objects, and use cases while preserving tenant isolation.

Core Features & Use Cases

• Resource Entity Pattern describes how to create entities with tenant IDs, state validation, primitive conversion helpers, and rich business methods without direct dependencies on NestJS or Prisma.
• Immutable Value Objects enforce validation rules in their constructors so names, IDs, and statuses always stay valid and thread-safe within SaaS modules.
• Repository Ports and Pure Use Cases lay out tenant-aware contracts and minimal orchestration logic so services such as auth, club, inventory, booking, and finance can avoid side effects while returning primitives.

Quick Start

Create a Resource entity using immutable value objects, a tenant-scoped repository, and a pure use case matching the described pattern.