Skip to main content
Use config validate after editing supaschema.config.json. The command loads config, checks path and source relationships, and reports warnings or errors before a migration command depends on it. It also blocks pending first-run path confirmation. If .supaschema/install.json says pathConfirmationNeeded: true, set schemaPaths, sources.to, and migrationsDir explicitly in supaschema.config.json before running zero-source migration commands.

​
Use this when

  • Schema or migration paths changed.
  • Source defaults changed.
  • Named environments were added.
  • Agent or CI automation needs structured config diagnostics.

​
Run it

npx supaschema config validate
npx supaschema config validate --json
npx supaschema --config config/supaschema.config.json config validate

​
Flags

​
--json
boolean
Print { "ok": boolean, "diagnostics": [...] }.

​
Exit codes

CodeMeaning
0Config is valid, with or without warnings
1Runtime failure
2Config diagnostics contained an error

Configuration

Review the config contract and defaults.

Environments

Configure named database targets.

Doctor

Diagnose config plus local environment.

Init

Scaffold or repair the generated setup.
Last modified on June 17, 2026