npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-verify-env

v1.0.0

Published

Verify all environment variables used in the project exist in .env

Readme

✅ node-verify-env

npm version npm downloads license

Verify that all environment variables used in your Node.js project exist in your .env file.
Catch missing configuration before runtime and avoid surprises in production.


📦 Installation

# Using npm
npm install --save-dev node-verify-env

# Using yarn
yarn add --dev node-verify-env

🚀 Usage

✅ CLI

Run in your project root:

npx node-verify-env

Example Output:

Scanning for environment variables...
Found 3 env variables in code.
❌ Missing environment variables in .env file:
- DB_PASSWORD
- API_KEY

If all variables exist:

✅ All required environment variables are present.

CLI Options

| Option | Description | |--------------------|--------------------------------------------| | --project-path | Path to scan (default: current directory) | | --env-path | Path to .env file (default: .env) | | --ignore | Comma-separated vars to ignore |

Example:

npx node-verify-env --project-path ./src --env-path ./config/.env --ignore OPTIONAL_VAR,DEBUG

✅ Programmatic API

import verifyEnv from "node-verify-env";

await verifyEnv({
  projectPath: "./src",      // Directory to scan (default: process.cwd())
  envPath: ".env",           // Path to .env file (default: ".env")
  ignore: ["OPTIONAL_VAR"]   // Variables to ignore
});

📄 Example

.env

DB_HOST=localhost
DB_USER=root

index.js

console.log(process.env.DB_HOST);
console.log(process.env.DB_PASSWORD); // Missing in .env
console.log(process.env.SERVICE_KEY); // Missing in .env

Run:

npx node-verify-env

Output:

Scanning for environment variables...
Found 3 env variables in code.
❌ Missing environment variables in .env file:
- DB_PASSWORD
- SERVICE_KEY

🔍 How It Works

  • Scans your code for process.env.VAR_NAME
  • Collects all variable names
  • Reads your .env file
  • Prints missing variables
  • Exits with status code 1 if any variables are missing (perfect for CI/CD)

🛠 Features

✔ Works with any Node.js project
✔ Detects missing env vars before runtime
✔ CLI + programmatic usage
✔ TypeScript support
✔ Great for CI/CD pipelines


📦 Add to CI/CD

Example for GitHub Actions:

- name: Verify Environment Variables
  run: npx node-verify-env

📌 Roadmap

  • [ ] Add support for import.meta.env (Vite/Frontend projects)
  • [ ] Add config file support for custom settings
  • [ ] Add option for .env.example validation

🛠 Contributing

Pull requests are welcome! For major changes, open an issue first to discuss what you would like to change.


📜 License

MIT © Shriram Sunil Khandbahale