Small CLI that checks process.env usage against .env.example.

CLI tool to synchronize .env and .env.example files

Validate .env files against .env.example with schema rules, env-specific checks, and CI-friendly output.

Validate .env against .env.example

Generate env.example from .env.<env> files

1. Setup .env from the .env.example

Keep your .env in sync with .env.example

Watches over your env vars — scan & generate .env.example on every commit

Generate .env.example from .env files with masked values

Lint, diff, sync, type, run, encrypt and protect your .env files — catch missing keys, duplicates, syntax slips, unresolved ${refs} and committed secrets; run commands with a merged env; encrypt/decrypt, compare environments, generate .env.example, export

Keep your env schema, .env.example, and process.env references honest with each other.

A linter for .env files to ensure consistency with .env.example

Detect and fix drift between your .env, .env.example, and the env vars your code actually uses.

Generates .env.example from your .env file

Trace environment variables and sync with .env.example

Keep .env and .env.example files in sync

CLI to generate .env.example files from existing .env sources.

Simple executable script to write "flows" .env.example environment configuration file.

Необходимо сообщить вашему node-процессу переменные окружения, перечисленные в `.env.example`.

A simple CLI tool to validate .env files against .env.example