Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: node-config/node-config
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.2.1
Choose a base ref
...
head repository: node-config/node-config
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.3.0
Choose a head ref
  • 17 commits
  • 21 files changed
  • 1 contributor

Commits on Jan 20, 2026

  1. Adding benchmarking tool to compare performance between PRs, trunk, and 

    released versions of node-config.
    @jdmarshall
    jdmarshall committed Jan 20, 2026
    Configuration menu
    Copy the full SHA
    9f803ad View commit details
    Browse the repository at this point in the history

  2. PR feedback

    @jdmarshall
    jdmarshall committed Jan 20, 2026
    Configuration menu
    Copy the full SHA
    8d33ee1 View commit details
    Browse the repository at this point in the history

Commits on Jan 24, 2026

  1. Upgrade faceoff to get statistical analysis. 

    Tweak tests to reduce inconclusive outcomes.
    @jdmarshall
    jdmarshall committed Jan 24, 2026
    Configuration menu
    Copy the full SHA
    81b7519 View commit details
    Browse the repository at this point in the history

  2. Expose GC to make the get() tests more accurate.

    @jdmarshall
    jdmarshall committed Jan 24, 2026
    Configuration menu
    Copy the full SHA
    0734bd7 View commit details
    Browse the repository at this point in the history

Commits on Feb 10, 2026

  1. Merge pull request #868 from jdmarshall/benchmarks 

    Adding benchmarking tool to compare performance between PRs and releases
    @jdmarshall
    jdmarshall authored Feb 10, 2026
    Configuration menu
    Copy the full SHA
    64206b3 View commit details
    Browse the repository at this point in the history

  2. Support callback functions for config files that need to use deferCon… 

    …fig()

This should answer #740 and also opens the door for migrating to ESM modules.

This does not at present address the issue of async.
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    0e8237e View commit details
    Browse the repository at this point in the history

  3. Clean up awaitDeferredConfig to more resemble awaitAsyncConfig. 

    And move some integration tests to unit tests.

Prep work for adding async support to defer()
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    b69441d View commit details
    Browse the repository at this point in the history

  4. Support async functions in deferConfig as a way to replace async.js 

    This is prep work for fixing #740
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    d5c5666 View commit details
    Browse the repository at this point in the history

  5. Update copyright notices to 2026

    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    5c0972e View commit details
    Browse the repository at this point in the history

  6. Move defer.js to lib

    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    ede4550 View commit details
    Browse the repository at this point in the history

  7. Deprecate defer.js

    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    5cd516c View commit details
    Browse the repository at this point in the history

  8. Allow new async mechanism to override old, instead of vice versa. 

    This will probably be better overall for anyone doing an incremental
migration since the new code will run last.
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    c6df6c6 View commit details
    Browse the repository at this point in the history

  9. Support for the 'Future Compatibility' contract in the project wiki. 

    https://github.com/node-config/node-config/wiki/Future-Compatibility

"If it's possible to detect your application using a future incompatibility,
a one-time warning per application run will be placed onto console.error for
each type of incompatibility.
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    c30a565 View commit details
    Browse the repository at this point in the history

  10. Add runtime deprecation warnings, as per 

    https://github.com/node-config/node-config/wiki/Future-Compatibility
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    55d17ba View commit details
    Browse the repository at this point in the history

  11. Fix issue with arrays of promises. 

    Fixes #876
    @jdmarshall
    jdmarshall committed Feb 10, 2026
    Configuration menu
    Copy the full SHA
    df3866b View commit details
    Browse the repository at this point in the history

Commits on Feb 12, 2026

  1. Merge pull request #863 from jdmarshall/deferredESM 

    Support callbacks in config JS/TS/ files to avoid the need for require() in config files
    @jdmarshall
    jdmarshall authored Feb 12, 2026
    Configuration menu
    Copy the full SHA
    bd4d95d View commit details
    Browse the repository at this point in the history

  2. prepare 4.3.0

    @jdmarshall
    jdmarshall committed Feb 12, 2026
    Configuration menu
    Copy the full SHA
    ce4fcf4 View commit details
    Browse the repository at this point in the history
Loading