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

Update Node.js to v20.19.0 #6

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

Update Node.js to v20.19.0 #6

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 16, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 20.12.2 -> 20.19.0 age adoption passing confidence
node (source) engines minor 20.12.2 -> 20.19.0 age adoption passing confidence
@types/node (source) devDependencies minor 20.12.14 -> 20.17.30 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 is behind base branch, 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 added the renovate label Jun 16, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 10 times, most recently from f74b17b to e0f95ba Compare June 20, 2024 18:18
@renovate renovate bot changed the title Update dependency node to v20.14.0 Update dependency node to v20.15.0 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 0056cc7 to a192b60 Compare June 26, 2024 02:34
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 34bc61c to 940921d Compare July 6, 2024 00:14
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 6c50f00 to 49641c9 Compare July 8, 2024 19:47
@renovate renovate bot changed the title Update dependency node to v20.15.0 Update dependency node to v20.15.1 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 8f18dfb to 0e05f21 Compare July 16, 2024 15:22
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0e05f21 to 546d196 Compare July 16, 2024 23:09
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2764d54 to 94818f9 Compare January 23, 2025 10:16
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 848fa7e to 35384a8 Compare February 10, 2025 17:13
@renovate renovate bot changed the title Update Node.js to v20.18.2 Update Node.js to v20.18.3 Feb 10, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 4bff510 to 27b4ec8 Compare February 14, 2025 03:39
@renovate renovate bot changed the title Update Node.js to v20.18.3 Update dependency @types/node to v20.17.19 Feb 21, 2025
@renovate renovate bot changed the title Update dependency @types/node to v20.17.19 Update dependency @types/node to v20.17.20 Feb 28, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from 27b4ec8 to 7ea33ed Compare February 28, 2025 21:30
@renovate renovate bot changed the title Update dependency @types/node to v20.17.20 Update dependency @types/node to v20.17.21 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7ea33ed to 9f4ca01 Compare March 1, 2025 01:24
@renovate renovate bot changed the title Update dependency @types/node to v20.17.21 Update dependency @types/node to v20.17.22 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 51d0068 to 286ea66 Compare March 3, 2025 18:03
@renovate renovate bot changed the title Update dependency @types/node to v20.17.22 Update Node.js to v20.18.3 Mar 3, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 4888583 to 9ef3757 Compare March 8, 2025 14:55
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9ef3757 to db96b84 Compare March 13, 2025 15:01
@renovate renovate bot changed the title Update Node.js to v20.18.3 Update Node.js to v20.19.0 Mar 13, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from e985da6 to f828a6d Compare March 27, 2025 03:23
@renovate renovate bot force-pushed the renovate/node-20.x branch from f828a6d to b995aeb Compare April 1, 2025 06:02
@renovate renovate bot force-pushed the renovate/node-20.x branch from b995aeb to 0039f4b Compare April 1, 2025 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants