Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2023

This PR contains the following updates:

Package Type Update Change Age Confidence
node (source) minor 20.15.1 -> 20.19.5 age confidence
@types/node (source) devDependencies minor 20.14.11 -> 20.19.25 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: 2025-07-15, Version 20.19.4 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • (CVE-2025-27210) Windows Device Names (CON, PRN, AUX) Bypass Path Traversal Protection in path.normalize()
Commits

v20.19.3: 2025-06-23, Version 20.19.3 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.19.2: 2025-05-14, Version 20.19.2 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
Commits

v20.19.1: 2025-04-22, Version 20.19.1 'Iron' (LTS), @​UlisesGascon prepared by @​RafaelGSS

Compare Source

Notable Changes
Commits

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.
It now no longer emits a warning unless --trace-require-module is explicitly used.
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: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 5b3a538 to 3e103d8 Compare December 3, 2023 19:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from 3e103d8 to 0d3e3bb Compare December 7, 2023 11:20
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0d3e3bb to ba8712d Compare December 17, 2023 22:04
@renovate renovate bot force-pushed the renovate/node-20.x branch from ba8712d to 3b64da7 Compare December 30, 2023 00:30
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 11f656a to f8a6627 Compare January 11, 2024 06:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from f653bb8 to 2a15df5 Compare January 17, 2024 11:44
@renovate renovate bot force-pushed the renovate/node-20.x branch 8 times, most recently from 91f658b to 6b5fee2 Compare January 31, 2024 00:54
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1024cdc to 9895b6b Compare February 2, 2024 17:57
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 3830f03 to aba0ced Compare February 15, 2024 19:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from aba0ced to 84ad9f7 Compare February 22, 2024 18:53
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from d60b151 to 1f19347 Compare July 1, 2025 23:54
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from c7c8ed2 to 0093c0d Compare July 15, 2025 12:15
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0093c0d to f7e3abd Compare July 15, 2025 22:54
@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 from f7e3abd to 8e7b96f Compare July 19, 2025 01:45
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from ddb1ece to 0659ead Compare August 15, 2025 09:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0659ead to 3e16776 Compare September 6, 2025 23:27
@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 4 times, most recently from f7ec285 to d200f20 Compare September 18, 2025 02:11
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 7e1df25 to c8128da Compare October 1, 2025 01:43
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 79badd9 to be32e48 Compare October 11, 2025 16:48
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 50098ff to 12bec62 Compare October 21, 2025 01:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from 12bec62 to cc64749 Compare October 28, 2025 19:11
@renovate renovate bot force-pushed the renovate/node-20.x branch from cc64749 to ff6af00 Compare November 10, 2025 16:51
@renovate renovate bot force-pushed the renovate/node-20.x branch from ff6af00 to 842ff7b Compare November 12, 2025 02:15
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.

1 participant