Skip to content
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

fix(deps): update node.js to v20.19.0 #14

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node (source) 20.5.1 -> 20.19.0 age adoption passing confidence
@types/node (source) 20.5.7 -> 20.17.24 age adoption passing confidence

Release Notes

nodejs/node (node)

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-lockfile branch 3 times, most recently from 2f7d028 to 6d57263 Compare February 15, 2024 18:25
@renovate renovate bot changed the title fix(deps): update node.js to v20.11.0 fix(deps): update node.js to v20.11.1 Feb 15, 2024
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 5 times, most recently from 3549b8d to 5477cfc Compare February 29, 2024 17:36
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from a0f48af to 82b4f41 Compare March 12, 2024 00:16
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 4 times, most recently from d9790f8 to a1b29f6 Compare March 19, 2024 13:37
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from a1b29f6 to 443562e Compare March 27, 2024 01:51
@renovate renovate bot changed the title fix(deps): update node.js to v20.11.1 fix(deps): update node.js to v20.12.0 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 5 times, most recently from 8962d26 to 03c9c94 Compare April 4, 2024 01:22
@renovate renovate bot changed the title fix(deps): update node.js to v20.12.0 fix(deps): update node.js to v20.12.1 Apr 4, 2024
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 4 times, most recently from 70425fe to 3df0b1c Compare April 11, 2024 04:21
@renovate renovate bot changed the title fix(deps): update node.js to v20.12.1 fix(deps): update node.js to v20.12.2 Apr 11, 2024
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from 2d59d30 to c9e03ba Compare May 6, 2024 16:30
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from 107b8b8 to 6d71a05 Compare November 21, 2024 04:21
@renovate renovate bot changed the title fix(deps): update node.js to v20.18.0 fix(deps): update node.js to v20.18.1 Nov 21, 2024
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 3 times, most recently from 6bb5f04 to 62f45ee Compare November 28, 2024 06:46
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from 62f45ee to e0d98bf Compare December 11, 2024 11:23
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from 9acb85c to 7dc9464 Compare January 6, 2025 12:22
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from 5eaedc4 to ce99bcb Compare January 16, 2025 01:11
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from ce99bcb to a737a84 Compare January 22, 2025 01:48
@renovate renovate bot changed the title fix(deps): update node.js to v20.18.1 fix(deps): update node.js to v20.18.2 Jan 22, 2025
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from ad29d62 to 7408c1e Compare January 30, 2025 19:43
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from 9ea6e7d to 8f41035 Compare February 9, 2025 12:35
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from 8f41035 to be3bda4 Compare February 11, 2025 00:50
@renovate renovate bot changed the title fix(deps): update node.js to v20.18.2 fix(deps): update node.js to v20.18.3 Feb 11, 2025
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from ac574dc to 524e1f8 Compare February 14, 2025 02:59
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 5 times, most recently from 300f3a2 to b523671 Compare March 3, 2025 19:57
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch 2 times, most recently from 776d413 to e3350a1 Compare March 11, 2025 10:52
@renovate renovate bot force-pushed the renovate/node-20.x-lockfile branch from e3350a1 to 1ca7da0 Compare March 14, 2025 01:26
@renovate renovate bot changed the title fix(deps): update node.js to v20.18.3 fix(deps): update node.js to v20.19.0 Mar 14, 2025
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