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 #318

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 22, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 20.11.1 -> 20.19.0 age adoption passing confidence
@types/node (source) dependencies minor 20.11.19 -> 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.

Copy link

vercel bot commented Feb 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
wallet-api ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 13, 2025 2:16pm
wallet-api-wallet-api-tools ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 13, 2025 2:16pm

Copy link

changeset-bot bot commented Feb 22, 2024

⚠️ No Changeset found

Latest commit: f18624f

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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 changed the title fix(deps): update dependency @types/node to v20.11.20 fix(deps): update dependency @types/node to v20.11.21 Feb 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from a8daed9 to 2416bec Compare February 28, 2024 00:36
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.21 fix(deps): update dependency @types/node to v20.11.22 Feb 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 2416bec to 18ff31d Compare February 28, 2024 18:03
@renovate renovate bot force-pushed the renovate/node-20.x branch from 18ff31d to ea669f2 Compare February 29, 2024 12:12
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.22 fix(deps): update dependency @types/node to v20.11.23 Feb 29, 2024
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.23 fix(deps): update dependency @types/node to v20.11.24 Feb 29, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from ea669f2 to a458e0a Compare February 29, 2024 17:43
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.24 fix(deps): update dependency @types/node to v20.11.25 Mar 6, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from a458e0a to 52c5089 Compare March 6, 2024 18:45
@renovate renovate bot force-pushed the renovate/node-20.x branch from 52c5089 to 3c961f5 Compare March 12, 2024 01:13
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.25 fix(deps): update dependency @types/node to v20.11.26 Mar 12, 2024
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.11.26 fix(deps): update dependency @types/node to v20.11.27 Mar 13, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 3c961f5 to abd7203 Compare March 13, 2024 14:35
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8c9292e to 9f80bc8 Compare February 13, 2025 07:26
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9f80bc8 to 281d5fe Compare February 14, 2025 01:53
@renovate renovate bot changed the title fix(deps): update node.js to v20.18.3 fix(deps): update dependency @types/node to v20.17.19 Feb 19, 2025
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.17.19 fix(deps): update dependency @types/node to v20.17.21 Feb 28, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from 281d5fe to 56777af Compare February 28, 2025 23:28
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.17.21 fix(deps): update dependency @types/node to v20.17.22 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from 56777af to 5448911 Compare March 1, 2025 10:05
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5448911 to f47fd46 Compare March 3, 2025 17:26
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v20.17.22 fix(deps): update node.js to v20.18.3 Mar 3, 2025
@renovate renovate bot force-pushed the renovate/node-20.x branch from f47fd46 to bd9f4fa Compare March 3, 2025 23:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from bd9f4fa to 9a64c23 Compare March 8, 2025 10:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9a64c23 to f18624f Compare March 13, 2025 14:14
@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 13, 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