Developer Tools●●Solid
VSCode .env Autocomplete
Scans code for variable usage to autocomplete .env keys automatically.
Solve My ProblemCozy
chrillemn
203mo ago
Back to browse
GitHub Repository
Catch missing and unused environment variables against your .env file
4 starsTypeScript
Environment Helper (VS Code)
by chrillemn·Apr 15, 2026·1 point·1 comment
AI Analysis
●●SolidSolve My ProblemCozy
Monorepo-aware .env validation with autocomplete from actual code usage.
Strengths
- •Nearest-.env resolution handles monorepos without manual configuration.
- •Autocomplete suggestions derived from scanned code references, not guesses.
- •Zero-config setup works immediately after install.
Weaknesses
- •Only supports .env files, ignores other secret management approaches.
- •No CI integration for catching issues before merge.
Category
Target Audience
Full-stack developers, DevOps engineers
Similar To
dotenv-linter · VS Code Dotenv extension
Similar Projects
Developer Tools●Mid
VSCode Extension for .env
Yet another .env linter, but monorepo nearest-file resolution is actually useful.
Cozy
chrillemn
1010d ago
Developer Tools●●Solid
Envsleuth – catch missing env vars before they reach production
AST parser catches missing env vars before you deploy to production.
Solve My ProblemShip It
k38f
101mo 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
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●●Solid
new version of dotenv-diff
Catches .env misconfigs early with SvelteKit and Next.js-specific rules.
Solve My ProblemNiche Gem
chrillemn
103mo ago