Validate your environment variables, JSON/YAML configs, file paths, and runtime versions before running — so you catch misconfig before it breaks production.
Deployments fail because a .env variable is missing, a JSON config is malformed, or the runtime is the wrong version — and you only find out after the container starts. badgr-config-doctor runs these checks in under a second, before you deploy.
Confirms each key in --required-env exists in process.env and is non-empty.
Parses --json-text / --yaml-text for validity and confirms --runtime matches the installed Node/Python version.
Prints a per-check result and exits 1 if anything failed, so it can gate a deploy or a badgr run step.
npx badgr-config-doctor --required-env API_KEY,DATABASE_URLRequires Node.js 18+.
Pass the checks you care about as flags — required env vars, config text, or a runtime requirement — and combine them in one command.
npx badgr-config-doctor \
--required-env API_KEY,DATABASE_URL \
--runtime node@20 \
--jsonbadgr-config-doctor
✓ API_KEY set
✗ DATABASE_URL missing — add to .env or CI secrets
✓ JSON config valid
✗ Runtime node@18 found, node@20 required
2 failures. Fix before deploying.badgr-config-doctor --required-env <keys>Check that comma-separated env var names are set and non-empty.badgr-config-doctor --json-text / --yaml-text <str>Validate a JSON or YAML config string parses without errors.badgr-config-doctor --runtime node@20Check the installed Node/Python version meets the requirement.npx badgr-config-doctor --required-env API_KEY,DATABASE_URL — no account needed to get started.