Keep .env complete without overwriting local values

At a glanceCopy Anchor Link

• Who: Teams whose .env.example gains keys across pulls and whose local .env must stay complete.
• What: Copy .env.example on first run, then append missing keys only — existing values are never overwritten.
• Use when: At the start of dev / build so a new example key cannot silently fall back to a default.
• Avoid when: When env files are generated another way (direnv, a secret manager, a deploy hook).
• See also: Fail CI when secrets are tracked

InstallCopy Anchor Link

pnpm add @zedtech/zedkit-quality

Latest: 1.1.0 (via changesets).

ExampleCopy Anchor Link

// package.json
{
  "scripts": {
    "dev": "zedkit-sync-env && next dev"
  }
}

Wraps: (none)