Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(deps): update node.js to 20.19#210

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
renovate wants to merge1 commit intomain
base:main
Choose a base branch
Loading
fromrenovate/node-20.x

Conversation

@renovate
Copy link
Contributor

@renovaterenovatebot commentedMar 3, 2025
edited
Loading

This PR contains the following updates:

PackageTypeUpdateChange
node (source)enginesminor20.11 ->20.19

Release Notes

nodejs/node (node)

v20.19.5: 2025-09-03, Version 20.19.5 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.19.4

Compare Source

v20.19.3

Compare Source

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 outsidenode_modules for the first time, it will emit an experimental warning unlessrequire() comes from a path that containsnode_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 throwERR_REQUIRE_ESM ifrequire() is used to load a ES module. It can, however, throwERR_REQUIRE_ASYNC_MODULE if the ES module being loaded or its dependencies contain top-levelawait. When the ES module is loaded successfully byrequire(), the returned object will either be a ES module namespace object similar to what's returned byimport(), or what gets exported as"module.exports" in the ES module.

Users can checkprocess.features.require_module to see whetherrequire(esm) is enabled in the current Node.js instance. For packages, the"module-sync" exports condition can be used as a way to detectrequire(esm) support in the current Node.js instance and allow bothrequire() andimport to load the same native ES module. Seethe 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 parentpackage.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 nearbypackage.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

Configuration

📅Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦Automerge: Enabled.

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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated byMend Renovate. View therepository job log.

@renovaterenovatebot changed the titlechore(deps): update node.js to 20.18chore(deps): update node.js to 20.19Mar 14, 2025
@sonarqubecloud
Copy link

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant


[8]ページ先頭

©2009-2025 Movatter.jp