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

chore(deps): update node.js to v20.19.0 #289

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2023

This PR contains the following updates:

Package Type Update New value References Sourcegraph Change Age Adoption Passing Confidence
node (source) minor 20.19.0 homepage, source code search for "node" 20.17.0 -> 20.19.0 age adoption passing confidence
@types/node (source) devDependencies minor 20.17.27 homepage, source code search for "@types/node" 20.16.10 -> 20.17.27 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.


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 - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, 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 ef29c65 to 187f542 Compare November 7, 2023 21:40
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from cddd4fc to 5c7a106 Compare November 23, 2023 22:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3fd6b10 to 892d8bb Compare November 29, 2023 19:50
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from e335228 to a56212c Compare December 7, 2023 07:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from a56212c to c3cf452 Compare December 18, 2023 00:21
@renovate renovate bot changed the title chore(deps): update dependency node to v20 chore(deps): update dependency node to v20.10.0 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3ab6deb to 9518b89 Compare December 22, 2023 07:25
@renovate renovate bot changed the title chore(deps): update dependency node to v20.10.0 chore(deps): update node.js to v20.10.0 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 9 times, most recently from 8c1b790 to 0299041 Compare December 31, 2023 01:54
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 608134d to 57385a2 Compare January 1, 2024 00:07
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from d8b250e to 4e33b9b Compare January 6, 2025 11:36
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a847154 to e835ddc Compare January 16, 2025 02:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from e835ddc to 56f7771 Compare January 21, 2025 19:26
@renovate renovate bot changed the title chore(deps): update node.js to v20.18.1 chore(deps): update node.js to v20.18.2 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0317cf6 to ebe141d Compare January 23, 2025 11:46
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a2ba9ea to ff4258e Compare February 10, 2025 14:54
@renovate renovate bot changed the title chore(deps): update node.js to v20.18.2 chore(deps): update node.js to v20.18.3 Feb 10, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from fd86455 to f07ca5a Compare February 14, 2025 00:34
@renovate renovate bot changed the title chore(deps): update node.js to v20.18.3 chore(deps): update dependency @types/node to v20.17.19 Feb 19, 2025
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.17.19 chore(deps): update dependency @types/node to v20.17.21 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from f07ca5a to 740f8fe Compare March 1, 2025 01:07
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.17.21 chore(deps): update dependency @types/node to v20.17.22 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from bfb44d5 to d72d833 Compare March 3, 2025 14:33
@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 5384186 to a012305 Compare March 8, 2025 08:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from a012305 to a146af6 Compare March 13, 2025 17:18
@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 2 times, most recently from ad638d8 to 22144e9 Compare March 24, 2025 08:37
@renovate renovate bot force-pushed the renovate/node-20.x branch from 22144e9 to 1d1c809 Compare March 24, 2025 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants