Skip to content

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

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 24, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 20.15.1 -> 20.19.2 age adoption passing confidence
node (source) engines minor 20.15.1 -> 20.19.2 age adoption passing confidence
@types/node (source) devDependencies minor 20.14.12 -> 20.17.57 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.

@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from cef65ff to 860a526 Compare August 2, 2024 10:40
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 229e9d0 to 81015c0 Compare August 9, 2024 18:22
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 0bba86f to fbeb386 Compare August 21, 2024 19:22
@renovate renovate bot changed the title Update dependency node to v20.16.0 Update dependency node to v20.17.0 Aug 21, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 817d373 to 618a4fd Compare September 1, 2024 12:33
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a6045d9 to d0c79ef Compare September 5, 2024 00:19
@renovate renovate bot force-pushed the renovate/node-20.x branch from d0c79ef to 6aa3fa2 Compare September 18, 2024 05:23
@renovate renovate bot changed the title Update dependency node to v20.17.0 chore(deps): update dependency node to v20.17.0 Sep 18, 2024
@alexanderniebuhr alexanderniebuhr force-pushed the main branch 6 times, most recently from 7e87dd6 to 03aa80c Compare September 23, 2024 06:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 72e3180 to 9593e0b Compare September 27, 2024 18:08
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9593e0b to aba82e0 Compare October 3, 2024 18:22
@renovate renovate bot changed the title chore(deps): update dependency node to v20.17.0 chore(deps): update dependency node to v20.18.0 Oct 3, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from aba82e0 to a687184 Compare October 7, 2024 22:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from a687184 to ae460a4 Compare October 17, 2024 01:32
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 33a0a6c to cb816d4 Compare March 27, 2025 07:03
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2a229e3 to 14e629c Compare April 1, 2025 23:00
@renovate renovate bot force-pushed the renovate/node-20.x branch from 14e629c to 7909309 Compare April 22, 2025 11:54
@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 6451ef4 to d821423 Compare April 28, 2025 08:13
@renovate renovate bot force-pushed the renovate/node-20.x branch 7 times, most recently from 7285c40 to f9aef30 Compare May 8, 2025 17:00
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 965474e to 4c24f34 Compare May 14, 2025 23:53
@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 fdf1817 to c1a0275 Compare May 21, 2025 04:13
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 21c8409 to 5bf354b Compare May 30, 2025 18:20
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5bf354b to e816fa7 Compare May 30, 2025 23:26
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