create-backend-entity-with-global-type

To keep NestJS TypeORM entities and frontend TypeScript types synchronized, generate both simultaneously using shared package export conventions, ensuring API response models and database schemas align. This prevents inconsistent backend models and frontend contracts.

TypeScript interfaces belong in shared-types packages when frontend applications consume the API response models, enums, or union types. Place interfaces in backend-only modules when the types represent internal database logic or schemas not exposed to the frontend.

To create a NestJS TypeORM entity with BaseCustomEntity inheritance, apply TypeORM decorators, define database schema columns, add indexes, and handle enums. This pattern ensures consistent entity creation across feature module development.

Yes, this approach works for generating TypeScript enums and API response models. It establishes a unified contract by creating database schemas alongside shared types, ensuring type alignment between backend and frontend applications.

The best way to structure a new feature module is to define the TypeORM entity with decorators and BaseCustomEntity inheritance first, then extract the shared TypeScript types and enums into a shared-types package for monorepo export.

Backend models and frontend contracts become inconsistent when database schemas and API response models are maintained separately without shared TypeScript types. Synchronizing TypeORM entities and frontend types prevents this drift.