CLI tool that scans your codebase for environment variable issues
1 points
1 hour ago
| 1 comment
| npmjs.com
| HN
chrilleweb
1 hour ago
[-]
Hello everyone,

I recently built a tool that I personally needed for my own projects, and now I’m super curious if other developers would actually find it useful.

It’s called dotenv-diff, and the main feature is a codebase scanner that finds problems with environment variables before they break things.

Why I built it

I kept seeing the same issues in real projects:

Feature breaks because .env is missing variables

New developer joins → app crashes due to missing env

.env.example goes out of sync

Someone accidentally leaves a secret inside a TS file

Frontend frameworks misused env naming (NEXT_PUBLIC, VITE_, etc.)

I wanted one CLI command that gives me a full health check of environment usage in my project.

Honest question:

Would this be useful in your workflow?

If you want to check it out:

npm package: https://www.npmjs.com/package/dotenv-diff Docs: https://dotenv-diff-docs.vercel.app

reply