Node Config Battle

A scientific comparison of Node.js config packages ::

Compared packages

All tests/comparisons should include the following steps we selected as requirements to represent a reasonable workflow.

Define a hierarchical configuration file
Override one value with an environment variable
Override another key with provided command arguments
Override a few keys with additional file contents (for example local development environment definitions)
One key should be a password and its value should not be set within the JSON, but rather through an environment variable, if a supplied key is missing or has an incorrect value, fail fast with exception
Fail fast if one mandatoiry config key wasn't provided
Cast keys to specific pre-defined types
Define default values for keys

Name	Latest commit message	Commit time
Failed to load latest commit information.
.history	init	May 27, 2018
config	Added benchmark suite for all packages to root directory	Jun 18, 2018
packages	Added benchmark suite for all packages to root directory	Jun 18, 2018
.gitignore	init	May 27, 2018
LICENSE	init	May 27, 2018
README.md	Update README.md	Jun 3, 2018
package-lock.json	Added benchmark suite for all packages to root directory	Jun 18, 2018
package.json	Added benchmark suite for all packages to root directory	Jun 18, 2018
perf-benchmark.js