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

v1.0.4

Published

A module that performs deployment checks, based on info found on your .env files

Downloads

4

Readme

A nodeJS module that performs deployment checks, based on info found on your .env files

What is dotenv-check

Dotenv check is a node.js cli module, performing various checks on the environment variables that your application uses. It's functionality is based on the dotenv module's .env file structure, but it can also be used without it.

Install

npm install dotenv-check --save

Features

  • Validates .env files structure and variable names
  • Performs similarity checks on main and sample .env files
  • Checks if envs are correctly exported in your current environment
  • Scans your source code and checks that you have not used any variables that are not defined in your .env files

Prerequisites

For this module to work, you must create a .env.sample file with the environment variables that you use in your application. The file should keep the dotenv module file format. If you are already using dotenv module, you are good to go.

Configuration

In your package.json, create a script called dotenvCheck and make it run the following command dotenv-check You can now use the script wherever you want. We recommend that you use it in the post install hook, in your package.json file

This module takes four optional arguments

  • envFile [default: null] The env file that is used in your current environment. If you don't use dotenv in your staging/production environment, but export the variables in some other way, leave this empty
  • sampleEnvFile [default: '.env.sample'] The sample dotenv file.
  • checkEnvsExported [default: false] Whether to check that the vars found in your .env.sample file have been exported in your current environment
  • sourceCode [default: null]

The arguments must be passed in the npm script like this

dotenv-check --envFile=".env" --sampleEnvFile=".env.sample"

Usage

The module checks that the structure and the environemnt variables in your .env.sample (and your current environment .env file if envFile is provided) file(s) are correct.

If you provided the envFile, it will also check that these two files have exactly the same variables

If checkEnvsExported is set to true, it will try to find every variable name that was parsed from the .env.sample file in the process.env node.js variable

If you provide a sourceCode folder, it will scan all files with a .js extension recursively, and checks if there is any environment variable that is not present in the .env.sample file is used in the code (it excludes the comments)

If any of these checks fail, it will exit with a status of 1, else it will exit with a status of 0

Build project

npm run build

Run tests

npm run test

Build docs

npm run docs

Author

👤 George Koniaris

Show your support

Give a ⭐️ if this project helped you!


This README was generated with ❤️ by readme-md-generator