Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 8, 2024

This PR contains the following updates:

Package Type Update Change Age Confidence
node (source) minor 20.11.0 -> 20.19.5 age confidence
@types/node (source) devDependencies minor 20.11.14 -> 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 changed the title chore(deps): update dependency @types/node to v20.11.16 chore(deps): update dependency @types/node to v20.11.17 Feb 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a41b401 to 1dd172f Compare February 14, 2024 18:50
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.11.17 chore(deps): update dependency node to v20.11.1 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from ef35c64 to 28e4b1c Compare February 15, 2024 18:43
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 745adf1 to afca969 Compare February 29, 2024 17:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 0be9a23 to 8d68a9b Compare March 13, 2024 17:12
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 35f2114 to 758aad2 Compare March 19, 2024 17:59
@renovate renovate bot changed the title chore(deps): update dependency node to v20.11.1 chore(deps): update dependency node to v20.12.0 Mar 26, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 87b6a60 to 4b620f5 Compare March 30, 2024 07:11
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 37389a2 to 0ac7620 Compare April 3, 2024 16:25
@renovate renovate bot changed the title chore(deps): update dependency node to v20.12.0 chore(deps): update dependency node to v20.12.1 Apr 3, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 77f25cd to 0a793ed Compare April 10, 2024 20:36
@renovate renovate bot changed the title chore(deps): update dependency node to v20.12.1 chore(deps): update dependency node to v20.12.2 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0a793ed to f69821c Compare May 1, 2024 21:05
@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 3 times, most recently from 66ae0e4 to a3a4445 Compare July 1, 2025 23:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 3d88b04 to d3efebe Compare July 15, 2025 13:38
@renovate renovate bot force-pushed the renovate/node-20.x branch from d3efebe to b7bf776 Compare July 15, 2025 22:49
@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 b7bf776 to 13690b2 Compare July 19, 2025 01:36
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c57a874 to d87f9b0 Compare August 15, 2025 09:59
@renovate renovate bot force-pushed the renovate/node-20.x branch from d87f9b0 to b53c88c Compare September 6, 2025 23:32
@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 99cf221 to 9399c2e Compare September 18, 2025 00:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 880cedf to 87f8310 Compare October 1, 2025 01:53
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from fe561d4 to ba627c5 Compare October 11, 2025 17:30
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3e5eabf to 56a380f Compare October 21, 2025 01:01
@renovate renovate bot force-pushed the renovate/node-20.x branch from 56a380f to 31ba663 Compare October 28, 2025 20:55
@renovate renovate bot force-pushed the renovate/node-20.x branch from 31ba663 to 4ca0b7d Compare November 11, 2025 23:58
@renovate renovate bot force-pushed the renovate/node-20.x branch from 4ca0b7d to b8d0af7 Compare November 18, 2025 13:12
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