dsh-env-manager

Maintaining environment variables across a growing codebase is easy to get wrong. A missing key in .env or a stale one left behind can surface at deploy time, and manually grepping every file is tedious. dsh-env-manager turns that routine check into two quick, local tools.

The env_check tool scans your source files for the common reference patterns — process.env.X, process.env["X"], import.meta.env.X, os.environ["X"], os.getenv("X") and similar — then cross-references them against your .env file. The result is a clear two-part list: variables referenced in code but absent from .env, and keys present in .env that no code actually uses. Directories such as node_modules and .git, along with binary and image assets, are skipped automatically so the output stays focused.

The env_example tool covers another recurring pain point: producing a safe .env.example before pushing to a repository. It reads your existing .env, keeps every key name, and replaces each value with a redacted placeholder, yielding a shareable template with zero secrets. The entire plugin is pure Node with no network calls and no external service dependencies — everything runs locally. It fits well with developers who want a fast pre-commit sanity check on their variable coverage, and with small teams that need a consistent, leak-free template across multiple repositories.