v5.0.0-alpha.2

What's Changed

• fix: prevent setEnv from clobbering envConfig when merging NODE_CONFIG
• .iced files are never loaded, and support has been removed.
• Load.scan() now returns the configuration data that was loaded, simplifying the calling convention for setModuleDefaults()
• TOML regression in 4.4.1 fixed in mainline

Breaking Changes

• Scanning of the config directory no longer loads files that contain the NODE_ENV value as a substring of the file name instead of the prefix. Ex: "prod-server1.js" versus "preprod.json" for NODE_ENV=prod

New Contributors

• @sputnik-mac made their first contribution in #896

Full Changelog: v5.0.0-alpha.1...v5.0.0-alpha.2

v4.4.2

What's Changed

• 4.4 branch: Guard against odd object prototype issues triggered by changes in TOML 4.0 by @jdmarshall in #916

Full Changelog: v4.4.1...v4.4.2

v5.0.0-alpha.1

What's Changed

• Fixed TS type list in README
• Fixed version tag issue

Full Changelog: v5.0.0-alpha.0...v5.0.0-alpha.1

v5.0.0-alpha.0

What's Changed

• node-config is now an ESM module

Breaking Changes

• raw.js, async.js, and defer.js have been replaced by the new callback mechanism
• config.util.setImmutable()
  • now only accepts one argument - an object. You can no longer use it to add immutable fields to config
  • array entries and the top level objects are now inextensible. They can no longer be amended after the fact.

Full Changelog: v4.4.1...v5.0.0-alpha.0

v4.4.1

What's Changed

• Fixes for some method signature declarations

Full Changelog: v4.4.0...v4.4.1

v4.4.0

What's Changed

• Typescript types added to project by @mdkitzman
• withModuleDefaults() function added to support separate module defaults for multiple versions
• Rework raw.js to function like the new defer mechanism.
• ./raw.js is also now deprecated, and will be removed in 5.0

New Contributors

• @mdkitzman made their first contribution in #877

Full Changelog: v4.3.0...v4.4.0

v4.3.0

What's Changed

• new callback mechanism for handling deferred and async configuration evaluation
• ./async.js and ./defer.js are now deprecated

New Async and Deferred mechanism

Instead of using async.js and defer.js, your executable config files can return a synchronous or asynchronous function. Note that if you use async deferred functions through the new mechanism, you need to call Util.resolveAsyncConfig() instead of the old version.

Util.resolveAsyncConfig() also fixes an issue where using defer in an array did not function properly #876

The old implementations have been marked as deprecated and will issue warnings to console.error to indicate use of the old pathways. The old functions are incompatible with ESM loading conventions and will be removed at the beginning of the 5.0 cycle to facilitate conversion of the library to ESM.

Full Changelog: v4.2.1...v4.3.0

v4.2.1

What's Changed

• Restore config.util.getEnv() by @jdmarshall in #874

Full Changelog: v4.2.0...v4.2.1

v4.2.0

What's Changed

• Delete deprecated functions in Config.util, and associated tests. by @jdmarshall in #845
• Default to yaml over js-yaml by @jdmarshall in #859

Breaking Changes

• All deprecated functions in config.util have been removed. Please use lib/util for similar functionality
• Default Yaml parser has changed to a more maintained alternative. Please validate your config files for correct processing, or adjust your package.json to force js-yaml to be used

Full Changelog: v4.1.1...v4.2.0

v4.1.1

What's Changed

This release includes only test and devDependency changes

• Remove vows from tests. by @jdmarshall in #854

Full Changelog: v4.1.0...v4.1.1