check
Validate Megamono repository structure
When to use it
Validate repository structure and configured policy. Keep this target non-cacheable and review the actual diagnostics. See governance enforcement and upgrade guidance for warning budgets, errors, consumer rule precedence, and package-source profiles.
Usage
Configure an Nx target on the owning project, then invoke it with npm exec -- nx run <project>:<target>. The executor identifier is not a standalone CLI command.
{
"targets": {
"reviewed-action": {
"executor": "@megamono/plugin:check",
"options": {}
}
}
}This target is a configuration example. Supply required values and review side effects before invoking it.
Options
Use these options with @megamono/plugin:check. Nx uses the camelCase names shown here; the CLI reference describes command-line aliases. Some options are required only for particular choices.
| Option | Required | Type | Default | Description |
|---|---|---|---|---|
config | No | string | "megamono.json" | — |
docsRoot | No | string | — | — |
skipDocs | No | boolean | false | — |
verbose | No | boolean | false | — |
ci | No | boolean | false | Reject development-only package addresses and verify registry routing plus the frozen lockfile. |
profile | No | string | — | Apply the named package-source policy profile. CI=true selects ci when omitted. Allowed: "development", "migration", "ci", "release". |
Next steps
Review changed files and run the affected project's checks. For options that accept structured values, run the generator's --help or consult the schema in the installed package.
