Developer Tools●Mid
VSCode Extension for .env
Yet another .env linter, but monorepo nearest-file resolution is actually useful.
Cozy
chrillemn
109d ago
Back to browse
GitHub Repository
Catch missing and unused environment variables against your .env file
4 starsTypeScript
VSCode .env Autocomplete
by chrillemn·Mar 11, 2026·2 points·0 comments
AI Analysis
●●SolidSolve My ProblemCozy
Scans code for variable usage to autocomplete .env keys automatically.
Strengths
- •Scans actual code usage to generate .env suggestions, not just syntax checking.
- •Monorepo support walks directory tree to find nearest .env file correctly.
- •Zero configuration required means it works immediately after installation without setup.
Weaknesses
- •No support for .env.example workflows or schema validation beyond existence checks.
- •Limited to local files, misses cloud secret management integration like Doppler.
Category
Target Audience
Backend developers, Full-stack developers
Similar To
DotENV · Env File · Doppler
Post Description
I am kinda proud of this simple tool - i would love to hear some feedback xD
Similar Projects
Developer Tools●●Solid
Environment Helper (VS Code)
Monorepo-aware .env validation with autocomplete from actual code usage.
Solve My ProblemCozy
chrillemn
112mo ago
Developer Tools●●Solid
Envguard – Like ESLint but for your environment variables
Code-scanning to auto-discover env vars beats manual .env validation.
Solve My ProblemShip It
Vamsha50
207d ago
Developer Tools●Mid
Env Validator (NextJS and SvelteKit)
Catches PUBLIC_ prefix misuse in SvelteKit when dotenv-linter exists.
Solve My Problem
chrillemn
201mo ago
Developer Tools●●Solid
Keep .env.example in sync with Codebase
Catches missing env vars and even warns when API keys expire.
Solve My Problem
chrillemn
112mo ago
Developer Tools●●Solid
new version of dotenv-diff
Catches .env misconfigs early with SvelteKit and Next.js-specific rules.
Solve My ProblemNiche Gem
chrillemn
103mo ago