Skip to content

chore(deps): update node.js to v20.19.2 #20

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 Jul 5, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) volta minor 20.15.0 -> 20.19.2 age adoption passing confidence
@types/node (source) devDependencies minor 20.14.9 -> 20.17.50 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

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

Compare Source

Notable Changes
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.

Copy link

changeset-bot bot commented Jul 5, 2024

⚠️ No Changeset found

Latest commit: 0f65074

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/node-20.x branch from 8e159a1 to 4fc5261 Compare July 8, 2024 22:28
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.14.10 chore(deps): update node.js to v20.15.1 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 4fc5261 to 729df6c Compare July 16, 2024 22:11
@renovate renovate bot force-pushed the renovate/node-20.x branch from 729df6c to 1751947 Compare July 23, 2024 22:39
@renovate renovate bot changed the title chore(deps): update node.js to v20.15.1 chore(deps): update node.js to v20.16.0 Jul 24, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a66d0c9 to 466426e Compare July 28, 2024 13:43
@renovate renovate bot force-pushed the renovate/node-20.x branch from 466426e to 58d024b Compare August 2, 2024 11:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 7956d17 to 080de94 Compare August 16, 2024 20:19
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 269e700 to 0b95489 Compare August 21, 2024 20:57
@renovate renovate bot changed the title chore(deps): update node.js to v20.16.0 chore(deps): update node.js to v20.17.0 Aug 21, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from a7d6183 to 97790aa Compare September 4, 2024 01:10
@renovate renovate bot force-pushed the renovate/node-20.x branch from 97790aa to 5ba062a Compare September 5, 2024 01:42
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 005ee17 to cc4443c Compare September 27, 2024 17:07
@renovate renovate bot force-pushed the renovate/node-20.x branch from cc4443c to 9ff5292 Compare October 3, 2024 18:19
@renovate renovate bot changed the title chore(deps): update node.js to v20.17.0 chore(deps): update node.js to v20.18.0 Oct 3, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9ff5292 to e8d3949 Compare October 8, 2024 00:34
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from a5fee97 to 526a859 Compare October 22, 2024 04:24
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from acae9a5 to 29c0730 Compare March 3, 2025 15:07
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.17.22 chore(deps): update node.js to v20.18.3 Mar 3, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0ed4762 to e7c0fb3 Compare March 8, 2025 11:00
@renovate renovate bot force-pushed the renovate/node-20.x branch from e7c0fb3 to a032dae Compare March 13, 2025 14:05
@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 3 times, most recently from 670c7e0 to db28218 Compare March 27, 2025 06:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a8b198c to 10a4920 Compare April 1, 2025 19:40
@renovate renovate bot force-pushed the renovate/node-20.x branch from 10a4920 to aca6bb8 Compare April 22, 2025 13:01
@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 2 times, most recently from c3d6d67 to c28c616 Compare April 28, 2025 07:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 7 times, most recently from e6e702e to 26c2289 Compare May 8, 2025 16:23
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from f2739d0 to fc24be5 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 2 times, most recently from 7594c45 to beca807 Compare May 20, 2025 22:52
@renovate renovate bot force-pushed the renovate/node-20.x branch from beca807 to 0f65074 Compare May 21, 2025 02:36
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