envy

// architecture

// overview

Every Node.js project has the same .env problems. Someone adds a variable and forgets to tell the team, staging breaks because a variable was renamed, a new developer clones the repo with no idea what belongs in .env. envy fixes this with a schema-driven format that describes every environment variable an app uses, then validates, audits, and codegens against it.

• ·A .env.schema format describing every variable an app needs: type, required/optional, format validators (postgresql-url, redis-url, jwt-secret, hex-color, semver, and more), plus modifiers like default, min/max, and enum.
• ·`envy audit` scans the entire codebase for process.env usage (including destructured and bracket-notation access) and flags anything used but not declared in the schema.
• ·`envy generate` produces a fully-typed src/env.ts that validates on import, so the app refuses to start with missing required variables.
• ·`envy sync` shares non-secret team defaults via a committed .env.team.json, without ever overwriting values a developer already has set locally.
• ·Zero runtime dependencies, fully tested, published to npm.