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

v0.0.3

Published

Simple module to test if current NODE_ENV is or is not within a list of allowed enviroments

Downloads

1,966

Readme

env-is

Simple module to test if current NODE_ENV is or is not within a list of allowed environments

Usage

It is simple as:

// for env = development
var env = require('env-is');

console.log(env.is('production')); // true if NODE_ENV is production
console.log(env.is(['production', 'staging'])); // true if NODE_ENV is production or staging

console.log(env.isNot('production')); // true if NODE_ENV is NOT production
console.log(env.isNot(['production', 'staging'])); // true if NODE_ENV is NOT production or staging

The return value of env.is will change depending on the value of NODE_ENV

NODE_ENV=production node app

Will return:

console.log(env.is('production')); //true
console.log(env.is(['production', 'staging'])); //true

console.log(env.isNot('production')); //false
console.log(env.isNot(['production', 'staging'])); //false

And

NODE_ENV=staging node app

Will return:

console.log(env.is('production')); //false
console.log(env.is(['production', 'staging'])); //true

console.log(env.isNot('production')); //true
console.log(env.isNot(['production', 'staging'])); //false

And...

NODE_ENV=development node app

Will return

console.log(env.is('production')); //false
console.log(env.is(['production', 'staging'])); //false

console.log(env.isNot('production')); //true
console.log(env.isNot(['production', 'staging'])); //true