Skip to content

chore(deps): update node.js to v20.19.5 #585

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update node.js to v20.19.5 #585

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2025 •
edited
Loading

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Type Update Change Age Confidence
node (source) minor 20.17.0 -> 20.19.5 age confidence
@types/node (source) devDependencies minor 20.17.22 -> 20.19.17 age confidence
node container minor 20.17.0 -> 20.19.5 age confidence

Release Notes

nodejs/node (node)

v20.19.5: 2025-09-03, Version 20.19.5 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.19.4

Compare Source

v20.19.3

Compare Source

v20.19.2

Compare Source

v20.19.1

Compare Source

v20.19.0: 2025-03-13, Version 20.19.0 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
require(esm) is now enabled by default

Support for loading native ES modules using require() had been available on v20.x under the command line flag --experimental-require-module, and available by default on v22.x and v23.x. In this release, it is now no longer behind a flag on v20.x.

This feature has been tested on v23.x and v22.x, and we are looking for user feedback from v20.x to make more final tweaks before fully stabilizing it. When the Node.js instance encounters a native ES module in require() somewhere outside node_modules for the first time, it will emit an experimental warning unless require() comes from a path that contains node_modules. If there happens to be any regressions caused by this feature, users can report it to the Node.js issue tracker. Meanwhile this feature can also be disabled using --no-experimental-require-module as a workaround.

With this feature enabled, Node.js will no longer throw ERR_REQUIRE_ESM if require() is used to load a ES module. It can, however, throw ERR_REQUIRE_ASYNC_MODULE if the ES module being loaded or its dependencies contain top-level await. When the ES module is loaded successfully by require(), the returned object will either be a ES module namespace object similar to what's returned by import(), or what gets exported as "module.exports" in the ES module.

Users can check process.features.require_module to see whether require(esm) is enabled in the current Node.js instance. For packages, the "module-sync" exports condition can be used as a way to detect require(esm) support in the current Node.js instance and allow both require() and import to load the same native ES module. See the documentation for more details about this feature.

Contributed by Joyee Cheung in #​55085

Module syntax detection is now enabled by default

Module syntax detection (the --experimental-detect-module flag) is now
enabled by default. Use --no-experimental-detect-module to disable it if
needed.

Syntax detection attempts to run ambiguous files as CommonJS, and if the module
fails to parse as CommonJS due to ES module syntax, Node.js tries again and runs
the file as an ES module.
Ambiguous files are those with a .js or no extension, where the nearest parent
package.json has no "type" field (either "type": "module" or
"type": "commonjs").
Syntax detection should have no performance impact on CommonJS modules, but it
incurs a slight performance penalty for ES modules; add "type": "module" to
the nearest parent package.json file to eliminate the performance cost.
A use case unlocked by this feature is the ability to use ES module syntax in
extensionless scripts with no nearby package.json.

Thanks to Geoffrey Booth for making this work on #​53619.

Other Notable Changes
  • [285bb4ee14] - crypto: update root certificates to NSS 3.107 (Node.js GitHub Bot) #​56566
  • [73b5c16684] - (SEMVER-MINOR) worker: add postMessageToThread (Paolo Insogna) #​53682
  • [de313b2336] - (SEMVER-MINOR) module: only emit require(esm) warning under --trace-require-module (Joyee Cheung) #​56194
  • [4fba01911d] - (SEMVER-MINOR) process: add process.features.require_module (Joyee Cheung) #​55241
  • [df8a045afe] - (SEMVER-MINOR) module: implement the "module-sync" exports condition (Joyee Cheung) #​54648
  • [f9dc1eaef5] - (SEMVER-MINOR) module: add __esModule to require()'d ESM (Joyee Cheung) #​52166
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Jun 1, 2025 •
edited
Loading

Important

Review skipped

Bot user detected.

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

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/node-20.x branch from 144c74c to b858c87 Compare June 6, 2025 21:36
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2168fe9 to ab2ca9e Compare June 23, 2025 12:52
@renovate renovate bot changed the title chore(deps): update node.js to v20.19.2 chore(deps): update node.js to v20.19.3 Jun 23, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c3cbe1f to 3c52955 Compare June 28, 2025 08:33
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2e3f14d to 1d45476 Compare July 8, 2025 20:00
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 3c953cd to b0b259b Compare July 15, 2025 23:56
@renovate renovate bot changed the title chore(deps): update node.js to v20.19.3 chore(deps): update node.js to v20.19.4 Jul 15, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0fee595 to be7f775 Compare July 19, 2025 01:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0f0968f to c225349 Compare August 15, 2025 09:46
@renovate renovate bot force-pushed the renovate/node-20.x branch from c225349 to 8fafe8a Compare August 17, 2025 00:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3bcf1d4 to 194fcdc Compare September 3, 2025 21:08
@renovate renovate bot changed the title chore(deps): update node.js to v20.19.4 chore(deps): update node.js to v20.19.5 Sep 3, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from a84f31e to 20a4176 Compare September 9, 2025 13:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 20e9e1d to 5294567 Compare September 16, 2025 13:47
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5294567 to 5fc8378 Compare September 17, 2025 02:36
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5fc8378 to 6f773d2 Compare September 18, 2025 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants