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

guardian-of-env

v1.2.8

Published

ensure .env files are all the same

Downloads

2

Readme

guardian-of-env

Build Status codecov version npm Renovate enabled

Screenshot

Screenshot

Installation

yarn add guardian-of-env --dev

Configuration

in your project folder, execute guardian-of-env, and guardian-of-env compares .env and .env.example file by default.

npx guardian-of-env

or set more files that you want to compare

npx guardian-of-env .env .env.example .env.exmaple.example

Work with pre-commit

install pre-commit first, and follow the configuration of package.json below

{
    "scripts": {
        "guardian-of-env": "guardian-of-env"
    },
    "pre-commit": [
        "guardian-of-env"
    ],
}

Work with travis-ci

or you want to compare your .env files in the ci phase

package.json

{
    "scripts": {
        "guardian-of-env": "./node_modules/.bin/guardian-of-env .env .env.test"
    },
}

.travis.yml

script:
- yarn guardian-of-env