Zero-config CLI to keep .env and .env.example in sync. Detects missing environment variables and fixes them interactively.

A tool that watches your .env file and updates your .env.example file

Generate .env.example easily

Create an .env.example with only keys from local .env

Your .env.example is the start gate - zero-dependency environment validation from the file you already maintain

A tiny command-line interface (CLI) to copy `.env.example` to `.env` in the current working directory if the `.env` file doesn't exist yet.

CLI tool to compare .env and .env.example files, reporting missing or extra keys to prevent environment variable bugs.

Checks your .env against your .env.example and tells you exactly what's missing, empty, or stale. Zero dependencies.

Automatically copy .env.example to .env.local in monorepo projects

Interactive CLI to generate your .env file from a .env.example by prompting for values.

``` npm install cp .env.example .env npm run dev ```

Schema-first settings for Node apps: cascading config across env files, per-env config files, and packages (monorepo extends). Zod validation, .env.example / Markdown docs / Kubernetes manifest generation, CLI for CI/CD.

Stop using process.env wrong. Zero-config TypeScript types from .env.example.

`.env.example` tracks the full variable inventory — copy it to `.env.local` and adjust. It also documents the variables `npm run dev-sv` injects (`VITE_APP_VERSION` from the manifest, `VITE_BUILD_SHA` from the current git commit) and the optional `VITE_`/

Pull .env updates from .env.example automatically. Keep your environment files in sync.

Generate .env.example from your project's env usage

Generate your .env.example file in a simple and fast way, you will never have to worry about manually updating your example file of environment variables!

Generate .env.example file from .env

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

Keep .env and .env.example honest: parse dotenv format, diff two files for drift and leak risk, and generate a safe .env.example. Zero runtime dependencies.