Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2025

This PR contains the following updates:

Package Type Update Change Pending Age Confidence
node (source) minor 20.18.2 -> 20.19.5 v20.19.6 age confidence
@types/node (source) devDependencies minor 20.17.16 -> 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: Enabled.

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 added the dependencies Changes to project dependencies label Feb 7, 2025
@renovate renovate bot enabled auto-merge (squash) February 7, 2025 04:36
@renovate renovate bot force-pushed the renovate/node-20.x branch from c317b87 to 1c6f479 Compare February 13, 2025 02:18
@renovate renovate bot changed the title Update dependency @types/node to v20.17.17 Update Node.js to v20.18.3 Feb 13, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2cd1e6c to 1758b3e Compare February 16, 2025 22:41
@renovate renovate bot changed the title Update Node.js to v20.18.3 Update dependency @types/node to v20.17.19 Feb 19, 2025
@renovate renovate bot changed the title Update dependency @types/node to v20.17.19 Update Node.js to v20.18.3 Mar 3, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from f444969 to b4d7499 Compare March 6, 2025 18:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 35f2e6c to bf25d87 Compare March 16, 2025 01:55
@renovate renovate bot changed the title Update Node.js to v20.18.3 Update Node.js to v20.19.0 Mar 16, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 904819d to 482c618 Compare March 30, 2025 05:56
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from fc0744e to 41f15e2 Compare April 4, 2025 17:42
@renovate renovate bot force-pushed the renovate/node-20.x branch from 41f15e2 to 21042e2 Compare April 25, 2025 01:56
@renovate renovate bot changed the title Update Node.js to v20.19.0 Update Node.js to v20.19.1 Apr 25, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 80d922b to fc98fdc Compare May 1, 2025 08:44
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 04b3691 to 75836d7 Compare May 11, 2025 05:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from bfb04c7 to 1c78b99 Compare June 26, 2025 01:10
@renovate renovate bot changed the title Update Node.js to v20.19.2 Update Node.js to v20.19.3 Jun 26, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 56ebd9a to 469268b Compare July 4, 2025 21:46
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 651e17a to eed0744 Compare July 18, 2025 04:01
@renovate renovate bot changed the title Update Node.js to v20.19.3 Update Node.js to v20.19.4 Jul 18, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from e3c0383 to 396e2d5 Compare July 22, 2025 02:06
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 16e5e93 to c9a3a63 Compare August 18, 2025 09:25
@renovate renovate bot force-pushed the renovate/node-20.x branch from c9a3a63 to f5f6f1e Compare September 6, 2025 19:05
@renovate renovate bot changed the title Update Node.js to v20.19.4 Update Node.js to v20.19.5 Sep 6, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from f5f6f1e to 23c2cd4 Compare September 7, 2025 14:02
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 1970676 to ac87d32 Compare September 21, 2025 00:49
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from dc316e1 to 86910fc Compare October 4, 2025 01:43
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0ba1b65 to 9e2f549 Compare October 14, 2025 14:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2ddf164 to ef65035 Compare October 24, 2025 04:37
@renovate renovate bot force-pushed the renovate/node-20.x branch from ef65035 to 554d6aa Compare October 31, 2025 18:54
@renovate renovate bot force-pushed the renovate/node-20.x branch from 554d6aa to 12802d0 Compare November 15, 2025 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Changes to project dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant