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

env-validator

v1.0.0

Published

Validates node version and environment variables required for app

Downloads

14

Readme

env-validator

Ensure that your Node app is running in a valid environment.

Call the validator to check that:

  • You're on the right Node version at runtime
  • All the required environment variables have been set

In an effort to fail fast, we check these two important features up front.

Install

npm install env-validator --save

Usage

Put the following function call close to the beginning of your program:

import validate from 'env-validator'

const env = {
  nodeVersion: '0.12.x'
  varNames: [
    'GITHUB_OAUTH_CLIENT_ID',
    'GITHUB_OAUTH_CLIENT_SECRET'
  ]
}
validate(env)

// the rest of your app below

Environment Config

Put the following properties in your env config object:

nodeVersion - (String) - Give a full major.minor.patch version of Node.js. Where you want to be variable, use an x, as in 0.13.x. Will throw an error if the Node version is not at least as high as what is expected. Compares with process.version.

varNames - (Array) - The names of environment variables that must be set in order for your app to work. Will throw an error indicating all the missing variables if they're not available from process.env.