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

envvar

v2.0.0

Published

Derive JavaScript values from environment variables

Downloads

3,098

Readme

envvar

envvar is a tiny JavaScript package for deriving JavaScript values from environment variables.

const envvar = require('envvar');

const GITHUB_API_TOKEN = envvar.string('GITHUB_API_TOKEN');
const HTTP_MAX_SOCKETS = envvar.number('HTTP_MAX_SOCKETS');
const ENABLE_FEATURE_X = envvar.boolean('ENABLE_FEATURE_X', false);

If one argument is provided the environment variable is required. If the environment variable is not set, an envvar.UnsetVariableError is thrown:

UnsetVariableError: No environment variable named "GITHUB_API_TOKEN"

If two arguments are provided the environment variable is optional. If the environment variable is not set, the default value is used. The default value must be of type Boolean in the case of envvar.boolean, of type Number in the case of envvar.number, or of type String in the case of envvar.string. If it is not, a TypeError is thrown.

The value of the environment variable must be the string representation of a value of the appropriate type: for envvar.boolean the only valid strings are 'true' and 'false'; for envvar.number applying Number to the string must not produce NaN. If the environment variable is set but does not have a suitable value, an envvar.ValueError is thrown:

ValueError: Value of process.env["HTTP_MAX_SOCKETS"] does not represent a number

envvar.oneOf

This is similar to envvar.string, but with constraints. There may be a small number of valid values for a given environment variable. For example:

const NODE_ENV = envvar.oneOf('NODE_ENV', ['development', 'staging', 'production']);

This states that process.env.NODE_ENV must be set to development, staging, or production.

A default value may be provided:

const NODE_ENV = envvar.oneOf('NODE_ENV', ['development', 'staging', 'production'], 'production');

This states that process.env.NODE_ENV must either be unset (in which case the default value is assumed), or set to development, staging, or production.