megamono init
Syntax, options, and usage for the init command.
Set up Megamono in an existing Nx workspace. Choose the conventions you want to use, such as project boundaries, documentation, and health checks.
Inspect your workspace first
bash
megamono init --surveyRead the project list and any questions about project ownership. For a small first adoption that keeps your current CI and release workflows, follow the adoption guide.
Command options
Use the help below for exact syntax and options. You can also run megamono init --help in your terminal.
text
Usage: megamono init [generator options]
Examples:
megamono init --survey
megamono init --profile=pilot --dry-run
megamono init --only=docs,agents --interactive=false --yes
megamono init --playstack --playstack-packages=auth
megamono init --playstack-packages=auth --playstack-web=apps/storefront --playstack-api=apps/gateway
megamono init --playstack --local-packages=yalc
megamono init --springbar --springbar-candidates=api,site --dry-run
The workspace must contain local Nx. A read-only survey uses the local plugin
when present, or stages a matching plugin in a disposable directory from the
selected registry/Yalc source. Mutation still requires a local plugin.
--springbar opts into Springbar-owned configuration after successful init.
--springbar-candidates selects exact names from Springbar inspection. Surveys
and dry runs inspect only; existing springbar.toml is never overwritten.
Springbar diagnostics go to stderr so survey JSON stdout remains pure.