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-safer

v1.0.0

Published

Load environment variables from a .env file with safety checks against an example file.

Readme

env-safer

A safer way to load and validate your environment variables in Node.js projects. Compare your .env file against an example file, check for missing or empty variables, and use it both as a library and a CLI tool.


Features

  • Ensures all variables in .env.example are present in your .env
  • Optionally checks for empty variables
  • Strict mode: throws on missing/empty variables
  • Loads .env variables using dotenv
  • Works as a Node.js library or CLI

How it works

When you use env-safer, your .env file is loaded using the dotenv package. This means all variables defined in your .env will be available globally in your Node.js process, just like with dotenv. The library then compares these variables to your .env.example to check for missing or empty values.


Installation

npm install env-safer

Or globally for CLI usage:

npm install -g env-safer

Usage

As a Node.js Library

import { loadSafeEnv, EnvValidationError } from "env-safer";

try {
  const result = loadSafeEnv({
    envPath: ".env", // optional, default: '.env'
    envExamplePath: ".env.example", // optional, default: '.env.example'
    checkEmpty: true, // optional, default: false
    strict: true, // optional, default: false
  });

  // result: { valid, missing, empty, env }
  console.log(result);
} catch (err) {
  if (err instanceof EnvValidationError) {
    console.error("Environment validation failed:", err.message);
  } else {
    throw err;
  }
}

As a CLI

After installing globally or as a project dependency, you can use the CLI:

env-safer --env .env --example .env.example --check-empty --strict

CLI Options

  • -e, --env <path>: Path to your .env file (default: .env)
  • -x, --example <path>: Path to your .env.example file (default: .env.example)
  • -c, --check-empty: Warn if variables exist but are empty
  • -s, --strict: Fail if there are empty or missing variables
  • -h, --help: Show help message

Example: Add to your package.json scripts

"scripts": {
  "check-env": "env-safer --env .env --example .env.example --check-empty"
}

Then run:

npm run check-env

API

loadSafeEnv(options)

  • envPath (string): Path to your .env file (default: .env)
  • envExamplePath (string): Path to your .env.example file (default: .env.example)
  • checkEmpty (boolean): If true, checks for empty variables (default: false)
  • strict (boolean): If true, throws EnvValidationError if invalid (default: false)

Returns:

{
  valid: boolean,
  missing: string[],
  empty: string[],
  env: object // parsed env variables
}

Throws EnvValidationError in strict mode if there are missing or empty variables.