Skip to content
This repository was archived by the owner on Jun 9, 2025. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2025

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines minor >=20.18.3 -> >=20.19.2 age adoption passing confidence
@types/node (source) devDependencies minor ^20.17.24 -> ^20.19.0 age adoption passing confidence
node final minor 20.18.3-alpine -> 20.19.2-alpine age adoption passing confidence

Release Notes

nodejs/node (node)

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 - "before 10:00 AM" (UTC), 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 from 9786a92 to 86141ff Compare March 21, 2025 11:09
@renovate renovate bot changed the title Update Node.js Update Node.js to >=20.19.0 Mar 21, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 78b532b to ee4bd22 Compare March 31, 2025 05:27
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 8606271 to 0042213 Compare April 7, 2025 05:37
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0042213 to d1540da Compare April 22, 2025 11:47
@renovate renovate bot changed the title Update Node.js to >=20.19.0 Update Node.js to >=20.19.1 Apr 22, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from fa14127 to acd5cdb Compare April 28, 2025 08:48
@renovate renovate bot force-pushed the renovate/node-20.x branch 11 times, most recently from da39754 to 8beaf81 Compare May 12, 2025 05:53
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c725f92 to d5d8ae2 Compare May 14, 2025 22:11
@renovate renovate bot changed the title Update Node.js to >=20.19.1 Update Node.js to >=20.19.2 May 14, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 2390e82 to ae1ccd6 Compare May 20, 2025 23:29
@renovate renovate bot force-pushed the renovate/node-20.x branch 8 times, most recently from e440b07 to 37295c2 Compare June 2, 2025 05:46
@renovate renovate bot force-pushed the renovate/node-20.x branch from 37295c2 to 9b9e5e6 Compare June 6, 2025 19:36
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9b9e5e6 to 21e5e5b Compare June 9, 2025 07:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant