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

v1.2.1

Published

A simple CLI tool to validate .env files against .env.example

Readme

env-escort

Overview

env-escort is a simple CLI tool that ensures all required environment variables are correctly set before running your application. It compares the .env file(s) with env.example and throws an error if any required variables are missing.

Features

  • Automatic Environment Validation: Ensures all necessary variables exist.
  • Checks .env File: Checks across .env.
  • Easy Integration: Can be added to the build pipeline to prevent missing environment configurations.

Installation

You can install env-escort locally in your project:

npm install env-escort --save-dev

Or install it globally:

npm install -g env-escort

Usage

1. Add an env.example File

Ensure your project has an env.example file listing all required environment variables:

DATABASE_URL=postgres://user:pass@localhost:5432/dbname
API_KEY=your-api-key
PORT=3000

2. Run env-escort in Your Project

Run the following command to check if all required environment variables are present:

npx env-escort check

If any required variables are missing, env-escort will throw an error and exit with status 1.

3. Add to package.json Scripts

To automatically check environment variables before building, update your package.json:

{
  "scripts": {
    "build": "env-escort check && your-build-command"
  }
}

Now, running npm run build will first validate environment variables.

Example Output

When all environment variables are set:

All required environment variables are set.

When some environment variables are missing:

ERROR: Missing environment variables: API_KEY, DATABASE_URL

How It Works

  1. Reads env.example to determine required environment variables.
  2. Checks .env for actual values.
  3. If any variables from env.example are missing, an error is thrown.

Contributing

We welcome contributions! To contribute:

  1. Fork this repository.
  2. Create a new branch (feature/my-feature).
  3. Make your changes and commit them.
  4. Open a pull request.

License

This project is licensed under the MIT License.


For any issues or suggestions, please open an issue.