v6.1.0

• feat: ✨ allow loading directly from a passed-in JSON object 17d3d2a
• fix: 🐛 set correct type for loadFromFiles 90ce7ee
• docs: 📚 add function doc for loadFromEnv 755fa75
• build: 📦 update dependencies e4db950

v6.0.0...v6.1.0

v6.0.0

• build!: 📦 update dependencies a6b09b8
  • Breaking change: Minimum required Node version is now Node 14

⭐️ This is the last major version to support CommonJS (CJS). Version 7 will be an ES Module.

v5.4.0...v6.0.0

v5.4.0

• feat: allow directly specifying the env 5e66940
  • You can now specify the env to use, by passing it as an option to the constructor. This overrides any NODE_ENV environment variable that is set. Previously, NODE_ENV was the only way to select an env.
    • example: const config = new Config({ env: 'your-env' });
• fix: disallow env names that conflict with builtin names f32ac48
  • env name default is disallowed because it conflicts with the config/default directory name
  • env name local is disallowed if loadLocalConfig is enabled, because it conflicts with the config/local directory name
• fix: properly handle env in the CLI utility 4a4cbb1
  • the CLI utility will now actually use the --env option

Other changes:

• chore: update Node.js version 3418fc4
• chore: update dependencies f6eb4b6
• feat: ignore options if they are explicitly set to undefined fb06dfb
• test: modernize use of assert 71d1f66

v5.3.0...v5.4.0

v5.3.0

• fix: make local parsing work correctly on the command-line f746a1a
• chore: update dependencies 8f6f027
• feat: upgrade js-yaml to v4 bc6a60a
• Bump ini from 1.3.5 to 1.3.7 1c5c3e8

v5.2.0...v5.3.0

v5.2.0

• feat: return the available keys for a config setting 885a2b2

API:

// get all the top-level keys for your config tree
const topKeys = config.keys();

// get the keys for the db section of your config tree
const dbKeys = config.keys('db');

Command-line:

# get the keys for the logging section of your config tree, as JSON
npx big-config keys logging --json

v5.1.0...v5.2.0

v5.1.0

• feat: ✨ add command-line utility e7239ff

To use the new big-config command line utility, type npx big-config.

There are many ways to use it. Here are some examples:

# show the available options
npx big-config --help

# get a specific config item (example: get development db settings)
npx big-config get db.development

# output JSON (example: get logging settings, print them as JSON)
npx big-config --json get logging

# output YAML (example: get AWS settings, print them as YAML)
npx big-config --yaml get aws

# get the entire config tree for the production environment as JSON — may be large
npx big-config get --env production --json

# show the default environment that will be used by big-config
npx big-config env

v5.0.0...v5.1.0

v5.0.0

• feat: option to control whether local settings are loaded 6f64c4c
• chore: upgrade dependencies 817dad4

⚠️ BREAKING CHANGE: Settings in the local directory will be loaded by default (similar to versions earlier than v4.0.0).

⚠️ BREAKING CHANGE: The BIG_CONFIG_ENABLE_LOCAL environment variable is no longer supported.

If you depend on BIG_CONFIG_ENABLE_LOCAL, do this for backward compatibility:

const shouldLoadLocalConfig = process.env['BIG_CONFIG_ENABLE_LOCAL'] === 'true';
const config = new Config({ loadLocalConfig: shouldLoadLocalConfig });

v4.0.0...v5.0.0

v4.0.0

• update dependencies and remove obsolete files ab6afa4
• added BIG_CONFIG_ENABLE_LOCAL env var 0b31fb6

v3.9.0...v4.0.0

• Breaking change: You now must set the environment variable BIG_CONFIG_ENABLE_LOCAL=true to use the local config directory. This change makes it safe to check files from local into Git. This allows you to set overrides in local for your developers, and those overrides won’t apply on your deployed environments.

v3.9.0

• dependencies updated

v3.6.0

• FIXED: properly resolve nested environment variables 7359fe9

v3.5.0...v3.6.0