Developer Tools●Mid
Env Validator (NextJS and SvelteKit)
Catches PUBLIC_ prefix misuse in SvelteKit when dotenv-linter exists.
Solve My Problem
chrillemn
201mo ago
Back to browse
GitHub Repository
Validate environment variable usage in codebase
51 starsTypeScript
Environment Variable Checker
by chrillemn·Mar 8, 2026·8 points·0 comments
AI Analysis
●●SolidSolve My ProblemNiche Gem
Catches env variable bugs early in SvelteKit/Next.js, but eslint-dotenv already does this.
Strengths
- •Framework-specific detection for SvelteKit/Next.js misuse (e.g., missing VITE_ prefix)
- •Monorepo support with shared folder inclusion; expiration warnings metadata for tokens/keys
- •Git hook and CI/CD integration; ignore comments for safe false positives
Weaknesses
- •Core problem (env variable mismatch) is well-solved by linters and dotenv plugins
- •Limited differentiation: validation logic is straightforward AST parsing, not novel
Category
Target Audience
JavaScript/TypeScript developers using Node.js, SvelteKit, Next.js, and monorepos
Similar To
eslint-dotenv · dotenv-expand · env-schema
Similar Projects
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
Developer Tools●Mid
VSCode Extension for .env
Yet another .env linter, but monorepo nearest-file resolution is actually useful.
Cozy
chrillemn
107d 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
Envguard – Like ESLint but for your environment variables
Code-scanning to auto-discover env vars beats manual .env validation.
Solve My ProblemShip It
Vamsha50
205d ago
Developer Tools●●Solid
VSCode .env Autocomplete
Scans code for variable usage to autocomplete .env keys automatically.
Solve My ProblemCozy
chrillemn
203mo ago