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

dotenv-lint

v1.0.1

Published

A tool for identifying issues with .env files in nodejs projects.

Downloads

8

Readme

dotenv-lint

npm build NPM code style: prettier

dotenv-lint is a tool for identifying issues with .env files in nodejs projects. It uses dotenv to read a master and one or more test .env files and compares them against each other according to a set of rules.

Installation

npm install --save-dev dotenv-lint

Usage

Imporant: By default, dotenv-lint runs in the current directory and uses .env.template as the*master and .env as the test.

dotenv-lint is primarily a CLI tool intended to be run via an NPM script:

{
    "scripts": {
        "start": "dotenv-lint && node ./app.js"
    }
}

It is a node binary which can also be invoked directly from the command line:

npx dotenv-lint [options] # using npx

dotenv-lint [options] # linked or installed globally

Options

  • path [p] - path to directory container .env files
  • master [m] - filename of master file
  • test [t] - filename(s) of test files
  • exit [e] - condition to exit with non-zero exit code (stops execution of npm script)
    • Options:
      • none - (default) always exit cleanly
      • error - exit(1) only if errors
      • warn - exit(1) if warnings

Examples

  • All default options

    dotenv-lint
    • In current directory, loads .env.template as the master and .env as the test
  • Specify path

    dotenv-lint --path ./my-package
    • In /my-package directory, loads .env.template as the master and .env as the test
    • Path supports relative and absolute paths
  • Specify master

    dotenv-lint --master .env.example
    • In current directory, loads .env.example as the master and .env as the test
  • Specify multiple tests

    dotenv-lint -p ./my-package -t .env.prod .env.dev
    • In the /my-package directory, loads .env.template as the master and .env.prod and .env.dev as tests
  • Stop NPM script on error

    dotenv-lint -e error