Security News
Supply Chain Attack Detected in Solana's web3.js Library
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
@logdna/env-config
Advanced tools
Node.js Package to define, document, and assert environment variables
$ npm install --save @logdna/env-config
$ npm t
The recommended way to structure applications with this package is as follows:
// config.js
'use strict'
const Config = require('@logdna/env-config')
const config = new Config([
Config.string('loglevel').default('info')
, Config.number('port').default(3000)
])
module.exports = config
// index.js
//
// The following env vars can be set:
//
// LOGLEVEL - defaults to info
// PORT - default to 3000
//
'use strict'
const http = require('http')
const config = require('./config.js')
// This validates that we have the necessary env vars.
config.validateEnvVars()
http.listen(config.get('port'), () => {
log.info('listen', config.get('port'))
})
Under the hood, Config
is a <Map>
, so use it like one.
This package also provides a way to automatically generate documentation for the environment variables for a service.
If the doc
directory does not exist, it can be created using the following:
$ mkdir -p doc
Then, add a generate
script to the
service's package.json
that looks similar to this:
config-doc config.js > doc/env.md
You should also add a link to this document in the README.md
of the service.
new Config(input)
input
<Array>
Array of objects that represent a single rule.Each input
item should be a Definition
. See "Static Methods" below.
The following static methods return a Definition
that can be used.
Config.string(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.This defines a configuration definition for an environment variable that is
a <String>
.
Returns: Definition
Config.number(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.This defines a configuration defintion for an environment variable that is
a <Number>
.
Returns: Definition
Config.boolean(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.This defines a configuration definition for an environment variable that is
a <Boolean>
.
Returns: Definition
Config.regex(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.This defines a configuration definition for an environment variable that
matches a <RegExp>
.
Returns: Definition
Config.enum(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.A single value will be read from the environment variable as described,
but it must exist in the allowed list of .values()
.
Every enum
type needs to implement a .values()
array.
Config.list(name)
name
<String>
Name of the config rule. The environment variable
read for this rule will be name
uppercased with -
replaced with _
.Much like a CSV - an environment variable will be read and parsed into an array
of a specific type. The type can be of string
, boolean
, or number
.
This is defined by calling .type()
.
All empty values generated by trailing characters are removed
Config#toJSON()
Returns a JSON representation of the config object. This will only work for Primitive values, objects, and arrays.
Config#validateEnvVars()
This should be called to validate that the required environment variables have been passed and that they satisfy the requirements. If any are not passed, or do not satisfy the requirements, an error will be thrown.
<TypeError>
| <RangeError>
| <RegExpError>
| <MissingEnvError>
| <EnumError>
| <RequiredDefaultMutexError>
This is a private prototype that offers the following methods:
Definition#required()
Specifies that this env var is required to have a value (env vars are optional by default). This means
that a value must be provided, and it cannot be the empty string, ''
.
Returns this
to allow chaining.
Definition#desc(str)
str
<String>
The descriptionThis sets the description for the env var that will be used for docs.
This is an alias for the Definition#description(str)
method.
Returns this
to allow chaining.
Definition#description(str)
str
<String>
The descriptionThis sets the description for the env var that will be used for docs.
Returns this
to allow chaining.
Definition#default(def)
This sets the default value of the rule. This does not set the actual env
var, but the value in the config's <Map>
will show the default value if the
env var's value is empty.
The default value will be applied for an unset var as well as a value of ''
.
Returns this
to allow chaining.
Definition#allowEmpty()
allowEmpty()
tells the definition to accept an empty value in place of the provided non-empty .default()
for cases where an empty value is valid and/or expected. Without this option, the default value will be used when
an empty value is detected for a given type. A common use for this is to allow ''
as a value for a
.string()
definition. In other words, allowEmpty()
is a no-op without a default()
.
The empty values for the config types supported by this package are as follows:
Type | Final Value |
---|---|
string | '' |
number | 0 |
boolean | false |
list | [] |
Definition#toJSON()
Returns a JSON representation of the configuration Definition
.
Definition#match(re)
This method can only be used with Config.regex()
. Otherwise, an error will
be thrown.
Returns this
to allow chaining.
Definition#min(n)
n
<Number>
The minimum value for the ruleThis method can only be used with Config.number()
. Otherwise, an error will
be thrown.
Returns this
to allow chaining.
Definition#max(n)
n
<Number>
The maximum value for the ruleThis method can only be used with Config.number()
. Otherwise, an error will
be thrown.
Returns this
to allow chaining.
Definition#values(arr)
arr
<Array>
An array of acceptable values for an enum
type.This method can only be used with Config.enum()
.
The final value must exist in the values arr
, or an error is thrown.
Definition#type(type)
type
<String>
The type of value expected within a list
can be one of:
number
boolean
string
Definition#separator(value)
default: /\s+|,/
'MissingEnvError'
This error is thrown if Definition#required
was used,
but no such environment variable or value was discovered.
'RequiredDefaultMutexError'
This error is thrown if Definition#required
and
Definition#default
are used together in a definition. A non-empty value must
be provided for required
variables, thus setting a default value for those
is a dead code path. These two options are mutually exclusive.
'RegExpError'
<Error>
name
<String>
Static value of RegExpError
expected
<RegExp>
The regular expression that is expected to
match the discovered valueactual
(Any) The value that was discovered in the environmentenv
<String>
The name of the evironment variable that is supposed
to hold the value (upper cased with underscores, e.g. MY_VARIABLE
)This error is thrown if Config.regex()
was used,
but the discovered value in the environment did not match the pattern.
'EnumError'
This error is thrown if Config.regex()
was used,
but the discovered value in the environment did not match the pattern.
'ListError'
<Error>
name
<String>
Static value of EnumError
expected
<Array>
The list of acceptable values for the definitionactual
(Any) An invalid value that found withing the listinput
<String>
The the value of the environment variable after it was parsed and sanitizedoriginal
<String>
The original value from the environment variabletype
<String>
The defined value type of the list propertyenv
<String>
The name of the evironment variable that is supposed
to hold the value (upper cased with underscores, e.g. MY_VARIABLE
)This error is thrown if Config.list()
was used,
but the discovered value in the environment contained an invalid value
Thanks goes to these wonderful people (emoji key):
Evan Lucas 💻 📖 | Darin Spivey 💻 📖 | Jacob Hull 🚧 | Eric Satterwhite 💻 |
This project follows the all-contributors specification. Contributions of any kind welcome!
FAQs
Configuration package for reading environment variables
We found that @logdna/env-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A supply chain attack has been detected in versions 1.95.6 and 1.95.7 of the popular @solana/web3.js library.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.