菜单
Implements the Repository pattern with TypeORM in NestJS so domain entities stay framework-free, ORM models live in infrastructure, and transactions are explicit. Use when adding persistence, refactoring leaky ORM usage, or handling transactions across aggregates.
| name | persisting-data-with-typeorm |
| description | Implements the Repository pattern with TypeORM in NestJS so domain entities stay framework-free, ORM models live in infrastructure, and transactions are explicit. Use when adding persistence, refactoring leaky ORM usage, or handling transactions across aggregates. |
| license | MIT |
@Entity() in domain)domain/@Entity()) live in infrastructure/application/ports/, TypeORM implementation in infrastructure/QueryRunner or @Transaction() decoratorexport class User {
private constructor(private id: string, private email: Email) {}
static create(id: string, email: Email): User { return new User(id, email); }
getEmail(): Email { return this.email; }
}
@Entity('users')
export class UserOrmEntity {
@PrimaryGeneratedColumn('uuid') id: string;
@Column() email: string;
@CreateDateColumn() createdAt: Date;
}
@Injectable()
export class TypeOrmUserRepository implements UserRepository {
constructor(@InjectRepository(UserOrmEntity) private repo: Repository<UserOrmEntity>) {}
async findById(id: string): Promise<User | null> {
const entity = await this.repo.findOne({ where: { id } });
return entity ? this.toDomain(entity) : null;
}
private toDomain(entity: UserOrmEntity): User {
return User.create(entity.id, Email.create(entity.email));
}
}
// ❌ ORM in domain
@Entity() export class User { @PrimaryColumn() id: string; } // Wrong!
See reference/typeorm-patterns.md for full patterns.
Defines the rule base every skill in this pack obeys: file layout, frontmatter, vocabulary, OOP/typing/decoupling axioms, and anti-patterns. Load FIRST before authoring or applying any other skill in this pack.
Designs NestJS feature modules with clean dependency boundaries, provider scopes, and dynamic modules. Use when adding a new feature module, splitting a monolithic AppModule, or fixing tangled imports between modules.
Builds thin NestJS controllers that parse input, invoke a single use case, and map the Result to ApiResponse<T>. Use when adding HTTP endpoints, refactoring fat controllers, or applying API versioning.
Prepares a NestJS service for production: graceful shutdown, health/readiness, structured logs, config, Dockerfile, CI gates, and rollout safety. Use when promoting a service to staging/production or auditing readiness.
Designs NestJS application services as use-case classes that orchestrate domain logic and ports without leaking the framework. Use when creating new use cases, refactoring services that mix HTTP/DB/domain, or moving from anemic services to OOP.
Maps internal AppError hierarchy to HTTP responses through a single global exception filter and a Result-to-HttpException helper. Use when adding new error types, fixing inconsistent error responses, or removing scattered try/catch in controllers.