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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@dhiyanesh/env-check

v1.0.2

Published

Ensure all .env variables are present in .env.example before commit

Downloads

13

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

dhiyaneshdhiyanesh

Keywords

envdotenvprecommithuskycheck

Readme

env-check (@dhiyanesh/env-check)

env-check is a simple CLI tool to ensure your .env.example file is in sync with your .env file. It can add missing variables, comment out extra ones, or remove them.

Installation

npm install -g @dhiyanesh/env-check

Usage

Run the CLI in your project root:

env-check [options]

Options

Add missing variables

env-check --add

Add missing variables from .env to .env.example.

Comment extra variables

env-check --remove

Comment out extra variables in .env.example.

Remove extra variables

env-check --remove-hard

Remove extra variables from .env.example.

Sync variables

env-check --sync

Add missing variables and comment extra ones.

Sync (with remove) extra variables

env-check --sync-hard

Add missing variables and remove extra ones.

Usage with husky

Add the following to husky pre-commit to automatically sync the .env and .env-example files before pushing your code.

npx env-check --sync-hard
git add .env.example

Notes

The tool requires .env file to exist in the project root.

After running, .env.example will be updated automatically.