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

dotenv-keys-diff

v1.0.0

Published

Compare .env and .env.example keys — find missing and extra variables.

Readme

dotenv-keys-diff

Compare .env and .env.example keys. Find variables missing from your local env or present in env but undocumented in the example file.

npm package name: dotenv-keys-diff (dotenv-diff was already taken). The dotenv-diff binary is also installed as an alias.

Install

npm install -g dotenv-keys-diff
# or one-shot:
npx dotenv-keys-diff

CLI

dotenv-keys-diff
dotenv-keys-diff --env .env.local --example .env.example
dotenv-keys-diff --check-empty
dotenv-keys-diff --json

| Option | Description | |--------|-------------| | --env <path> | Env file (default: .env) | | --example <path> | Example file (default: .env.example) | | --cwd <path> | Working directory | | --check-empty | Fail when env values are empty | | --allow-missing | Treat a missing .env as empty | | --json | Machine-readable output | | -q, --quiet | Suppress success message | | -h, --help | Help | | -v, --version | Version |

Exit codes: 0 match · 1 differences · 2 usage/file error

Example output

Missing in env (1) — present in example, absent in env:
  - DATABASE_URL
Extra in env (1) — present in env, absent in example:
  + DEBUG_SECRET

API

import { parseEnv, diffEnv, diffFiles } from "dotenv-keys-diff";

const env = parseEnv("FOO=1\nBAR=2\n");
const example = parseEnv("FOO=\nBAZ=\n");

const result = diffEnv(env, example);
// { missing: ["BAZ"], extra: ["BAR"], empty: [], ok: false }

const fromDisk = diffFiles({
  cwd: process.cwd(),
  env: ".env",
  example: ".env.example",
  checkEmpty: false,
});

CI

Fail the build when someone adds an env var without updating .env.example:

- run: npx dotenv-keys-diff --env .env.ci --example .env.example

Or keep example as the source of truth when CI has no .env:

npx dotenv-keys-diff --allow-missing

License

MIT