@danmasta/env v5.1.0

Env

Environment helper for node apps

Features:

• Easy to use
• Load .env, .js, .json, .cjs, or .mjs files
• Type coercion for primitive types
• Option for setting helper variables like NODE_ENV
• Optional command line helper --env for defining variables from argv
• Source of truth is always process.env
• Will not override existing variables
• Bash-like variable expansion via $var or ${var}
• Full character escape sequence support (unicode, hex, octal, single)
• Start of line and end of line comments are supported
• Support for multiline values
• Support for loading variables from vault
• Native esm and cjs support
• 0 external dependencies

About

I wanted a better way to interact with environment variables in node apps. This package aims to simplify the process while maintaining process.env as the source of truth. It can parse variables from .env, .js, .json, .cjs, or .mjs files, and it can also import variables from vault secrets. It supports type casting so you can use variables with boolean or number values as their native types. Variable expansion, multiline values, comments, and full character escape sequences are also supported.

Usage

Add env as a dependency for your app and install via npm

npm install @danmasta/env --save

Import or require the package in your app

import env from '@danmasta/env';

Get an environment variable

env('NODE_ENV');

Set an environment variable

env('NODE_ENV', 'development');

Options

Methods

Environment Files

By default this package will attempt to load environment files in the following order: 1. ./.env 2. ./config/.env 3. ./env.(js|json|cjs|mjs) 4. ./config/env.(js|json|cjs|mjs)

If multiple files are found, they do not overwrite each other. This package will respect the first value set for each key

Type Coercion

When values are set on process.env, by default they are always converted to a string. This makes it awkward when using boolean values or other primitive types. When getting a variable using this package, it will attempt to convert the value back to it's native type if desired. This includes: true, false, null, undefined, NaN, and number.

Escape Sequences

All escape sequences defined here are supported, including unicode code points, unicode escapes, hexidecimal escapes, octal escapes, and single character escapes.

Just use regular escape code format for values with escape sequences: \u{1d306}, \u2665, \xA5, \001, \n, \t, etc.

Variable Expansion

Bash-like variable expansion is supported in .env files. Just prefix a variable name with a $ sign or wrap it in ${var}. If you need to escape the $ sign just use regular escape format like other sequences: \$.

HOST=127.0.0.1
PORT=6379
REDIS_URL=redis://$HOST:$PORT
ESCAPED=\$ESCAPED

Helper Options

There are a few helper options you can use to set things like NODE_ENV and parse variables from argv:

let env = new Env({
    enableArgv: true
    setNodeEnv: true,
    helpers: ['DEVELOPMENT', 'PRODUCTION'],
});

This will let you use helper cli arguments to set variables when running your app:

node app --node-env=local --env=REDIS_HOST=127.0.0.1,REDIS_PORT=6379

Two other helper variables are also added: DEVELOPMENT, and PRODUCTION. They are boolean values which will be true if NODE_ENV matches their variable name, otherwise false.

Comments

Start of line and end of line comments are supported:

# Redis config
HOST=127.0.0.1
PORT=6379
REDIS_URL=redis://$HOST:$PORT # Expanded redis url

If you want to use the # symbol in a string, just wrap the string in single or double quotes:

TEST='This #comment will not be stripped'

Load Additional Files

If you want to load variables from other files programatically you can create a new instance and provide the files option with a list of files to load. By default paths in node are resolved using process.cwd. Home character expansion ~ is also supported.

let env = new Env({
    files: './config/production/.env'
});

await env.resovle();

Load Variables from Vault

This package also supports loading environment variables from vault. It will attempt to read the variables from a vault secret path, then parse the key/value pairs and set them in the environment. The vault api HTTP requests can be made asynchronously, or synchronously via a worker thread that has a default timeout of 2.5 seconds.

import { loadFromVault } from '@danmasta/env';

let token = '$VAULT_TOKEN';
let addr = '$VAULT_ADDR';

await loadFromVault('/env/app/prod', { token, addr });

The secret, token, and addr params can be set explicity when calling the function, or can be set as defaults when creating an env instance. It will also read from the VAULT_TOKEN and VAULT_ADDR environment variables, as well as the default token helper file location: ~/.vault-token.

Note: When loading secrets from vault, the api path is slightly different for kv v1 vs kv v2 (versioned) secrets

Example

If you had a kv v1 secret mount point of /env and you wanted to load the secret path /app/prod, you could use the whole path as-is:

await loadFromVault('/env/app/prod');

However, with kv v2, you need to append /data to the mount point. The above example would become:

await loadFromVault('/env/data/app/prod');

Sync

If your app is still cjs and/or doesn't support top level await, and you need to load variables from vault synchronously, you can do that too:

const { loadFromVaultSync } = require('@danmasta/env');

loadFromVaultSync('/env/app/prod');

Examples

Get an environment variable

env('NODE_ENV');

Set an environment variable

env('NODE_ENV', 'development');

Set multiple environment variables

env({
    REDIS_HOST: '127.0.0.1',
    REDIS_PORT: 6379
});

Load extra environment files

let env = new Env({
    files: './config/production/.env'
});

await env.resovle();

Load environment variables from vault

export VAULT_TOKEN="$TOKEN"
export VAULT_ADDR="https://vault.example.net"

await env.loadFromVault('/env/app/prod');

ESM

If running in esm mode, you should export your env config as default:

export default {
    REDIS_HOST: '127.0.0.1',
    REDIS_PORT: 6379
};

Load env variables dynamically from vault based on config settings

If you use a config library that supports loading js files you can use this package to load environment variables based on your config settings:

// ./config/local.js
import { loadFromVault } from '@danmasta/env';

await loadFromVault('/env/app/local');

export default {
    ...
};


// ./config/development.js
import { loadFromVault } from '@danmasta/env';

await loadFromVault('/env/app/dev');

export default {
    ...
};


// ./config/production.js
import { loadFromVault } from '@danmasta/env';

await loadFromVault('/env/app/prod');

export default {
    ...
};


// ./app.js
import env from '@danmata/env';
import config from '@danmasta/config';

app.listen(...);

Check if development environment using helper vars

env('DEVELOPMENT'); // true if NODE_ENV === 'development' otherwise false

Check if production environment using helper vars

env('PRODUCTION'); // true if NODE_ENV === 'production' otherwise false

Testing

Tests are currently run using mocha and chai. To execute tests run make test. To generate unit test coverage reports run make coverage

Contact

If you have any questions feel free to get in touch