Skip to content

chore(deps): update node.js to v20.19.3 #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

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.13.1 -> 20.19.3

Release Notes

nodejs/node (node)

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

v20.18.3: 2025-02-10, Version 20.18.3 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - "after 10am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 89bb6d1 to cb10cbb Compare March 13, 2025 13:46
@renovate renovate bot changed the title chore(deps): update node.js to v20.18.3 chore(deps): update node.js to v20.19.0 Mar 13, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from cb10cbb to a6dade4 Compare March 17, 2025 16:14
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 03d01e3 to 79ce897 Compare March 31, 2025 18:46
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from dbe7ec5 to e9f2f07 Compare April 7, 2025 22:34
@renovate renovate bot force-pushed the renovate/node-20.x branch from e9f2f07 to 9da3293 Compare April 22, 2025 12:00
@renovate renovate bot changed the title chore(deps): update node.js to v20.19.0 chore(deps): update node.js to v20.19.1 Apr 22, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 2658956 to 76e8792 Compare May 5, 2025 19:30
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 835feed to 246753d Compare May 14, 2025 23:50
@renovate renovate bot changed the title chore(deps): update node.js to v20.19.1 chore(deps): update node.js to v20.19.2 May 14, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 9675fee to 843bf74 Compare May 26, 2025 19:45
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2359460 to b7f264c Compare June 2, 2025 19:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 038dfed to bcce86e Compare June 23, 2025 14:03
@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 2 times, most recently from 7ba3656 to 98cb6f4 Compare June 30, 2025 22:27
@renovate renovate bot force-pushed the renovate/node-20.x branch from 98cb6f4 to f7f9b9e Compare July 7, 2025 16:02
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.

0 participants