Env

voltro env works with the typed-env manifest — the set of environment variables your app declares (via envVar(...)) and the framework requires. It's how a missing or malformed env var becomes a boot-time error with a clear message instead of a mysterious runtime failure.

voltro env            # check (default) — validate the current env against the manifest
voltro env check      # explicit
voltro env sync       # write/update .env.example from the manifest
voltro env types      # emit env.generated.d.ts (typed process.env for CI tsc)
voltro env turbo      # emit the turbo globalEnv/globalPassThroughEnv list

#check (default)

Validates the current environment against the declared manifest and fails (non-zero) on a missing required var or a value that doesn't parse. Run it in a pre-deploy step to catch a misconfigured environment before the app boots. Run with no subcommand and it defaults to check.

#sync — keep .env.example honest

Writes .env.example from the manifest so the committed template always matches what the app actually reads — new envVar(...) declarations show up without hand-editing.

#types — typed process.env for CI

Emits env.generated.d.ts, which types process.env to your declared vars. Commit it (or generate it in CI before tsc) so a typo in a process.env.MY_VAR reference is a type error, not a runtime undefined.

#turbo — monorepo cache correctness

Emits the globalEnv / globalPassThroughEnv entries for turbo.json, so Turbo's cache invalidates when a relevant env var changes and passes the right vars through to tasks.

#Related

• Secrets — generating secret values with voltro secret.
• Configuration — declaring env vars with envVar(...).