refactor: Bump config from 4.4.1 to 5.0.1

[dependabot]

Bumps config from 4.4.1 to 5.0.1.

Release notes

Sourced from config's releases.

v5.0.1

What's Changed

• Fix issue with async defers calls not being replaced in the config data.

New Contributors

• @​MMShep97 made their first contribution in node-config/node-config#926

Full Changelog: node-config/node-config@v5.0.0...v5.0.1

v5.0.0

The 5.0 release contains ESM support, removes some deprecations, strengthens some immutability constraints in a few call paths, and fixes some incorrect filename matches for files that only contain the NODE_ENV value but don't start with it.

What's Changed

• ESM conversion of node-config by @​jdmarshall in node-config/node-config#889
• fix: prevent setEnv from clobbering envConfig when merging NODE_CONFIG by @​sputnik-mac in node-config/node-config#896
• Removed .iced support by @​jdmarshall in node-config/node-config#902
• Improve ergonomics of setModuleDefaults/Load.scan() by @​jdmarshall in node-config/node-config#903
• fix: use anchored regex for NODE_ENV file matching (closes #867) by @​sputnik-mac in node-config/node-config#904
• Add perf test for the new scan changes. by @​jdmarshall in node-config/node-config#908
• Guard against odd object prototypes triggered by changes in TOML 4.0 by @​jdmarshall in node-config/node-config#917

New Contributors

• @​sputnik-mac made their first contribution in node-config/node-config#896

Full Changelog: node-config/node-config@v4.4.1...v5.0.0

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 node-config/node-config#896

Full Changelog: node-config/node-config@v5.0.0-alpha.1...v5.0.0-alpha.2

v5.0.0-alpha.1

What's Changed

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

Full Changelog: node-config/node-config@v5.0.0-alpha.0...v5.0.0-alpha.1

... (truncated)

Commits

• f89ef8b 5.0.1
• 8114c25 Merge pull request #926 from MMShep97/fix-resolve-async-configs
• 08edfa0 Merge pull request #928 from jdmarshall/workflowMain
• 9705d75 Fix workflow for PRs.
• 77b8752 Merge pull request #927 from jdmarshall/main
• 1cd86a7 Remove method signature change
• a06d897 Fix resolveAsyncConfigs leaving promises in the exported config
• fbb28f8 Release 5.0.0
• b4dfbd2 Merge pull request #923 from jdmarshall/supplyChain44
• 3a4851b Merge pull request #922 from jdmarshall/supplyChain
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 704de9e5-cf69-4e55-bb0d-53e19072a90c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.77%. Comparing base (d6f6d2a) to head (b5378cf).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #611   +/-   ##
=======================================
  Coverage   97.77%   97.77%           
=======================================
  Files           2        2           
  Lines         225      225           
=======================================
  Hits          220      220           
  Misses          5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mtrezza]

Cannot merge: config@5.0.1 requires Node >=20.19.0 but engines.node specifies >=20.18.0 <21.0.0 || >=22.12.0 <23.0.0 || >=24.11.0 <25.0.0.

config@5 declares engines.node >= 20.11.0, but since config@5.0.0 (ESM conversion, node-config/node-config#889) its CommonJS entry point lib/config.js is module.exports = require('./config.mjs').default, which needs require(esm) support. That is only available without a flag from Node 20.19.0 / 22.12.0.

config is loaded by spec/test.spec.js on every CI test job, and the Parse Server 8, Node.js 20 job (Node 20.18.0) fails with SyntaxError: Cannot use import statement outside a module when it loads config/lib/config.mjs. The same job passes on master. The newest version without this requirement is 4.4.2. Converting to draft until the minimum supported Node.js version is raised to 20.19.0.