Problem statement
NestJS is the most widely used opinionated Node.js framework. Developers starting a NestJS project still need to manually configure TypeScript, linting, architecture, and the module/controller/service structure.
Proposed solution
Implement NodeNestJSGenerator in generators/typescript/nestjs.go.
Name(): "node-nestjs"Language(): "typescript"Modules(): ["nestjs"]
Apply() generates a NestJS application with:
package.json (NestJS + TypeScript dependencies)tsconfig.json, nest-cli.jsonsrc/app.module.ts, src/main.ts- File structure adapted to
spec.Config.Architecture
Commands: new module <name>, new controller <name>, new service <name>
Alternatives considered
Use the NestJS CLI under the hood (nest new). Rejected — dot generates deterministic files from templates; executing external CLIs adds a runtime dependency.
Area
Core
Additional context
Uses static composition with TypeScript backend architecture generators. Depends on: TypeScript architecture generators.
Problem statement
NestJS is the most widely used opinionated Node.js framework. Developers starting a NestJS project still need to manually configure TypeScript, linting, architecture, and the module/controller/service structure.
Proposed solution
Implement
NodeNestJSGeneratoringenerators/typescript/nestjs.go.Name():"node-nestjs"Language():"typescript"Modules():["nestjs"]Apply()generates a NestJS application with:package.json(NestJS + TypeScript dependencies)tsconfig.json,nest-cli.jsonsrc/app.module.ts,src/main.tsspec.Config.ArchitectureCommands:
new module <name>,new controller <name>,new service <name>Alternatives considered
Use the NestJS CLI under the hood (
nest new). Rejected — dot generates deterministic files from templates; executing external CLIs adds a runtime dependency.Area
Core
Additional context
Uses static composition with TypeScript backend architecture generators. Depends on: TypeScript architecture generators.