Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2025

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.16.10 -> 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.

Copy link

coderabbitai bot commented Jun 1, 2025

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 bfadfba to fa05fde Compare June 6, 2025 21:21
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c56f536 to 05321ee Compare June 23, 2025 12:46
@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 0908e6c to a6c3fc2 Compare June 28, 2025 09:25
@renovate renovate bot force-pushed the renovate/node-20.x branch from a6c3fc2 to e882738 Compare July 1, 2025 20:45
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from f3c4067 to f74b9d4 Compare July 15, 2025 07:48
@renovate renovate bot force-pushed the renovate/node-20.x branch from f74b9d4 to 1106369 Compare July 16, 2025 03:36
@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 16, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from 1106369 to 6ce6654 Compare July 19, 2025 02:23
@renovate renovate bot force-pushed the renovate/node-20.x branch from 6ce6654 to e6d24dd Compare July 28, 2025 14:05
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from e0f62f5 to 1a5cf8e Compare August 15, 2025 14:39
@renovate renovate bot force-pushed the renovate/node-20.x branch from 1a5cf8e to 40f09d3 Compare August 16, 2025 21:15
@renovate renovate bot force-pushed the renovate/node-20.x branch from 40f09d3 to e575611 Compare September 6, 2025 18:53
@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 6, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 46c7df0 to 27689cc Compare September 13, 2025 23:27
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2c5985c to c04475c Compare September 17, 2025 00:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from c04475c to eb8b12c Compare September 18, 2025 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants