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 🙏

© 2024 – Pkg Stats / Ryan Hefner

compare-env-keys

v1.0.3

Published

A simple script you can use in your package.json to make sure that all the keys in a dotenv file are present in other dotenv files.

Downloads

29

Readme

compare-env-keys

A simple script you can use in your package.json to make sure that all the keys in a dotenv file are present in other dotenv files.

The use case for this is to run this script before you deploy a website or web application where you just to make sure your staging.env or production.env dotenv files have all the environment variables that are present in a local.env.

This helps prevent a deploy that fails in staging or production because an environment variable is missing.

Install

Install with npm:

$ npm install --save-dev compare-env-keys

Install with yarn:

$ yarn add --dev arr-diff compare-env-keys

Usage

In your package.json, add to scripts:

{
  // ...
  "scripts": {
    "predeploy:staging": "compare-env-keys env/local.env env/staging.env",
    "predeploy:production": "compare-env-keys env/local.env env/production.env",
    "predeploy:all": "compare-env-keys env/local.env env/staging.env env/production.env"
  }
}