creating-elysia-domains

Scaffolding an Elysia domain module involves generating a structured directory under apps/nexus/src/domains/<domain-name>/ with schema.ts, types.ts, service.ts, repository.ts, routes.ts, and index.ts files. This enforces strict Drizzle schema typing and enables Eden Treaty type inference for API consumers.

Structuring an Elysia API for Eden Treaty type inference requires separating code into repository, service, and route layers while defining strict Elysia t.* types for API contracts. This architecture guarantees type safety propagates automatically to consumers.

Domain scaffolding with Drizzle schemas works by enforcing strict type usage within Elysia API modules. It provides templates for repository and service layers that wrap Drizzle database schemas, ensuring consistent architecture and type-safe database interactions across the application.

Yes, you can use Elysia t.* types to define API contracts serving multiple consumers like dashboards and Discord bots. By applying strict type definitions in domain routes.ts and types.ts files, Eden Treaty compatibility is maintained across all consumer applications.

Yes, after scaffolding a new domain under apps/nexus/src/domains/<domain-name>/, you need to manually wire it into apps/nexus/src/app.ts. This integration step connects typed route handlers, service layers, and Drizzle schemas to the main Elysia application instance.