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

env-consistency

v1.1.0

Published

Ensure consistency across .env files based on a reference file.

Readme

env-consistency

A CLI tool to ensure your .env.* files are consistent with a reference, all via a simple npx command.

🔍 Why Use This

When you have multiple environment files (e.g., .env.local, .env.staging, .env.production), it's easy for keys to get out of sync. Missing or extra variables can cause bugs that only appear in specific environments.

⚠️ Note: All .env.* files must be located in the root directory of your project for the tool to work properly.

env-consistency helps by:

  • Comparing selected .env.* files against a reference (.env.dist by default).
  • Reporting missing or extra keys in each file.
  • Optionally adding missing keys with a default value (foo-bar).
  • Reordering keys to match the reference order (extras appended alphabetically).
  • Exiting with a non-zero status on inconsistencies (great for CI).

⚙️ Installation (Using npx)

No install required! Run directly with npx:

npx env-consistency

This will download and execute the latest version of the tool.

📦 Usage

Simply run:

npx env-consistency

You'll be prompted to:

  1. Select which .env.* files to check (e.g., local, staging, production, etc.).
  2. Enter the reference file name (defaults to .env.dist).

After selection, the tool will:

  • Log missing files, missing keys, and extra keys.
  • Ask if you'd like to auto-add missing keys with value foo-bar.
  • Reorder each file to match the reference key order.

On completion, it exits with:

  • 0 if all files are consistent.
  • 1 if any inconsistencies were found.

🚀 Example Session

$ npx env-consistency
🔧 env-consistency starting…
? Which .env files do you want to check? › ◉ local ◯ staging ◯ production
? Reference file to compare against: (.env.dist)

⚠️ Issues in .env.local:
  • Missing keys: API_KEY, TIMEOUT
  • Extra keys:   DEBUG_MODE
? Add missing keys to .env.local with value 'foo-bar'? › (Y/n) Y
    ✔ API_KEY=foo-bar added
    ✔ TIMEOUT=foo-bar added
🔄 .env.local reordered

✅ .env.staging: All keys match
✅ .env.production: All keys match

🎯 CI Integration

Use in your CI pipeline to fail builds on env mismatches:

- name: Check env consistency
  run: npx env-consistency

🤝 Contributing & Support

Contributions welcome! Open an issue or PR on the GitHub repo.


Published via env-consistency