chore(deps): update node.js to v20.19.0 #162
No reviewers
Labels
No Label
bug
doing
duplicate
enhancement
help wanted
invalid
question
ready
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kompetenzinventar/ki-frontend#162
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/node-20.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
20.18.1-alpine->20.19.0-alpine20.18.1-alpine->20.19.0-alpineRelease Notes
nodejs/node (node)
v20.19.0: 2025-03-13, Version 20.19.0 'Iron' (LTS), @marco-ippolitoCompare 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.
It now no longer emits a warning unless
--trace-require-moduleis explicitly used.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-moduleas a workaround.With this feature enabled, Node.js will no longer throw
ERR_REQUIRE_ESMifrequire()is used to load a ES module. It can, however, throwERR_REQUIRE_ASYNC_MODULEif 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 check
process.features.require_moduleto 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()andimportto 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-moduleflag) is nowenabled by default. Use
--no-experimental-detect-moduleto disable it ifneeded.
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
.jsor no extension, where the nearest parentpackage.jsonhas 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"tothe nearest parent
package.jsonfile 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
Commits
v20.18.3: 2025-02-10, Version 20.18.3 'Iron' (LTS), @marco-ippolitoCompare Source
Notable Changes
Commits
v20.18.2: 2025-01-21, Version 20.18.2 'Iron' (LTS), @RafaelGSSCompare Source
This is a security release.
Notable Changes
Dependency update:
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.
This PR has been generated by Renovate Bot.
f3b3a3114ato7922d096217922d09621toe76b20f7b8e76b20f7b8tob808d3597ab808d3597ato157c851230157c851230to695201d683chore(deps): update node.js to v20.18.2to chore(deps): update node.js to v20.18.3695201d683to2f569b211f2f569b211fto529e2691a0529e2691a0to7abe3470e17abe3470e1tob3b9de6dceb3b9de6dcetof796081996chore(deps): update node.js to v20.18.3to chore(deps): update node.js to v20.19.0f796081996toc4796e0d2cCheckout
From your project repository, check out a new branch and test the changes.