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-var-defaults

v0.0.1

Published

Give the env-var module different default values per current NODE_ENV.

Downloads

77

Readme

Env Var Defaults

Build Status Coverage Status

Give the env-var module different default values per current NODE_ENV. Can be also used independently.

Why

First of all, there's a rule of thumb:

Variables explicitly set in the environment always have final say.

We often use a great module, env-var, to read the environment variables and parse them, and if a variable is missing we can set a default value for it.

Sometimes we want to have environment specific defaults, which shouldn't override the environment variables but shouldn't be overridden by the default value either. This can lead to confusion as which override which and when to set default values etc.

How

// Require.
const { builder, injected } = require('env-var-defaults');

// The injected/augmented env-var.
const env = injected();

// Use it, and give it a list of default values.
const logStream = env.get('LOG_STREAM', ['debug', 'debug', 'syslog', 'syslog']).asString();

The "builder"

The builder is the base, and can be used independently. When invoked, it can give you a getter function:

const defaults = builder([envList, [envName]]);
  • envList is the list of ENV values, default to ['test', 'development', 'staging', 'production'].
  • envName is default to NODE_ENV.

Now you can use the function to get a value corresponding to the current ENV.

const value = defaults(['valueA', 'valueB', 'valueC', 'valueD']);
  • For example, with the default envList, and the ENV development, the value will be valueB.
  • Note that the ENV is used at build-time (when you run builder()), and not at run-time.

If you give the builder an env list:

const defaults = builder(['test', 'development', 'integration', 'staging', 'production']);

Then you must give the defaults a list of default values matches to it:

const value = defaults(['valueA', 'valueB', 'valueC', 'valueD', 'valueE']);
  • For example, with the ENV integration, the value will be valueC.

The "injected"

The injected can give you an augmented env-var:

const env = injected([envList, [envName]]);
  • It accepts the same arguments with builder.
  • It returns what env-var would give you with just the get() function augmented.

And you use it like the initial example:

const logStream = env.get('LOG_STREAM', ['debug', 'debug', 'syslog', 'syslog']).asString();

You can also use it in the original way, if you have just one default value:

const logStream = env.get('LOG_STREAM', 'debug').asString();