Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2025

This PR contains the following updates:

Package Update Change
node (source) minor 20 -> 20.19.5

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: 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 this update 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 Mar 3, 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.

Copy link

cypress bot commented Mar 3, 2025

next-core    Run #11700

Run Properties:  status check passed Passed #11700  •  git commit 757e5c4ff9 ℹ️: Merge 4460d34fc4cb76ec1ddf6244eec545956f63d597 into 800064a938cf1a07c6bfe6a8d768...
Project next-core
Branch Review renovate/next-node-20.x
Run status status check passed Passed #11700
Run duration 00m 25s
Commit git commit 757e5c4ff9 ℹ️: Merge 4460d34fc4cb76ec1ddf6244eec545956f63d597 into 800064a938cf1a07c6bfe6a8d768...
Committer renovate[bot]
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 17
View all changes introduced in this branch ↗︎

@renovate renovate bot force-pushed the renovate/next-node-20.x branch from 1e78aa1 to fbbf9e1 Compare March 13, 2025 16:29
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.18.3 (next) chore(deps): Update Node.js to v20.19.0 (next) Mar 13, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch from fbbf9e1 to b59a671 Compare April 22, 2025 16:09
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.19.0 (next) chore(deps): Update Node.js to v20.19.1 (next) Apr 22, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch 2 times, most recently from b46b4d1 to c209e36 Compare May 14, 2025 22:55
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.19.1 (next) chore(deps): Update Node.js to v20.19.2 (next) May 14, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch from c209e36 to 6db57a0 Compare June 23, 2025 13:08
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.19.2 (next) chore(deps): Update Node.js to v20.19.3 (next) Jun 23, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch from 6db57a0 to 3f68689 Compare July 16, 2025 02:32
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.19.3 (next) chore(deps): Update Node.js to v20.19.4 (next) Jul 16, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch from 3f68689 to 350c88b Compare September 3, 2025 20:45
@renovate renovate bot changed the title chore(deps): Update Node.js to v20.19.4 (next) chore(deps): Update Node.js to v20.19.5 (next) Sep 3, 2025
@renovate renovate bot force-pushed the renovate/next-node-20.x branch from 350c88b to 4460d34 Compare September 25, 2025 19:56
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