docfy init
Onboarding en un solo comando: conecta DocfyModule, decora los controllers, registra el plugin de webpack si es necesario, añade scripts a package.json y genera los archivos de documentación.
Uso
bash
npx nestjs-docfy init [options]El camino más rápido hacia un setup funcionando — reúne lo que generate --link-controller --register-plugin ya hacen, más el único paso nuevo: conectar DocfyModule.forRoot() en tu módulo raíz.
Qué hace
- Locates each app's bootstrap file and the class passed to
NestFactory.create(...), then wiresDocfyModule.forRoot()into that root module's@Module({ imports: [...] }). Static analysis only — never executes your code. If it can't locate the bootstrap file or the module with certainty, it warns and skips that app instead of guessing. - Runs the same steps as
generate --link-controller --register-plugin: decorates every controller with@WithDocs(), registers the webpack CLI plugin if needed, and generates the companion*.controller.docs.tsfiles. - Adds
docs:generate/docs:previewscripts to the rootpackage.json, without overwriting any script already defined under those names.
Every step is independently idempotent, so running init again is always safe — useful after adding a new controller or a second app to the project. See CLI: generate for what each bundled step does on its own.
Opciones
| Option | Default | Description |
|---|---|---|
--root <path> | . | Project root directory |
--tsconfig <path> | auto-detected | Path to tsconfig.json |
--pattern <glob> | **/*.controller.ts | Glob pattern to find controllers |
--format | ts | Output format: ts or js |
--dry-run | false | Print what would change without writing any files |
--quiet | false | Suppress all output except errors |