Envalid is a small library for validating and accessing environment variables in Node.js programs, aiming to:
envalid.cleanEnv(environment, validators, options)
cleanEnv()
returns a sanitized, immutable environment object, and accepts three positional arguments:
environment
- An object containing your env vars (eg. process.env
)validators
- An object that specifies the format of required vars.options
- An (optional) object, which supports the following keys:
strict
- If true, the output of cleanEnv
will only contain the env vars that were specified in the validators
argument.reporter
- Pass in a function to override the default error handling and console output. See lib/reporter.js
for the default implementation.transformer
- A function used to transform the cleaned environment object before it is returned from cleanEnv
By default, cleanEnv()
will log an error message and exit if any required env vars are missing or invalid.
const envalid = require('envalid')
const { str, email, json } = envalid
const env = envalid.cleanEnv(process.env, {
API_KEY: str(),
ADMIN_EMAIL: email({ default: 'admin@example.com' }),
EMAIL_CONFIG_JSON: json({ desc: 'Additional email parameters' })
})
// Read an environment variable, which is validated and cleaned during
// and/or filtering that you specified with cleanEnv().
env.ADMIN_EMAIL // -> 'admin@example.com'
// Envalid parses NODE_ENV automatically, and provides the following
// shortcut (boolean) properties for checking its value:
env.isProduction // true if NODE_ENV === 'production'
env.isTest // true if NODE_ENV === 'test'
env.isDev // true if NODE_ENV === 'development'
For an example you can play with, clone this repo and see the example/
directory.
Node's process.env
only stores strings, but sometimes you want to retrieve other types (booleans, numbers), or validate that an env var is in a specific format (JSON, url, email address). To these ends, the following validation functions are available:
str()
- Passes string values through, will ensure an value is present unless a default
value is given.bool()
- Parses env var strings "0", "1", "true", "false", "t", "f"
into booleansnum()
- Parses an env var (eg. "42", "0.23", "1e5"
) into a Numberemail()
- Ensures an env var is an email addressurl()
- Ensures an env var is a url with a protocol and hostnamejson()
- Parses an env var with JSON.parse
Each validation function accepts an (optional) object with the following attributes:
desc
- A string that describes the env var.choices
- An Array that lists the admissable parsed values for the env var.default
- A fallback value, which will be used if the env var wasn't specified. Providing a default effectively makes the env var optional.devDefault
- A fallback value to use only when NODE_ENV
is not 'production'
. This is handy for env vars that are required for production environments, but optional for development and testing.You can easily create your own validator functions with envalid.makeValidator()
. It takes a function as its only parameter, and should either return a cleaned value, or throw if the input is unacceptable:
const { makeValidator, cleanEnv } = require('envalid')
const twochars = makeValidator(x => {
if (/^[A-Za-z]{2}$/.test(x)) return x.toUpperCase()
else throw new Error('Expected two letters')
})
const env = cleanEnv(process.env, {
INITIALS: twochars()
});
You can, and should, also provide a type
with your validator. This can be exposed by tools to help other developers better understand you configuration options.
To add it, pass a string with the name as the second argument to makeValidator
.
const { makeValidator } = require('envalid')
const twochars = makeValidator(x => {
if (/^[A-Za-z]{2}$/.test(x)) return x.toUpperCase()
else throw new Error('Expected two letters')
}, 'twochars')
By default, if any required environment variables are missing or have invalid values, envalid will log a message and call process.exit(1)
. You can override this behavior by passing in your own function as options.reporter
. For example:
const env = cleanEnv(process.env, myValidators, {
reporter: ({ errors, env }) => {
emailSiteAdmins('Invalid env vars: ' + Object.keys(errors))
}
})
.env
File SupportEnvalid wraps the very handy dotenv package, so if you have a .env
file in your project, envalid will read and validate the env vars from that file as well.