Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.27.11
->2.28.1
20.17.16
->20.17.24
v0.0.22
->v0.0.26
v1.11.1
->v1.11.7
v4.1.0
->v4.3.0
v1.4.9
->v1.4.10
v1.28.0
->v1.37.0
20.18.2
->20.19.0
20.18.2
->20.19.0
9.15.4
->9.15.9
8.3.5
->8.4.0
5.7.3
->5.8.2
2.1.8
->2.1.9
Release Notes
changesets/changesets (@changesets/cli)
v2.28.1
Compare Source
Patch Changes
b9df596
]:v2.28.0
Compare Source
Minor Changes
84a4a1b
Thanks @bennypowers! - Added a new config option to opt-out from formatting with Prettier usingprettier: false
.Patch Changes
84a4a1b
,84a4a1b
]:v2.27.12
Compare Source
Patch Changes
#1562
a0f87f1
Thanks @Netail, @cefn! - Fixed changelog application when executing usingnpx
and similar toolsUpdated dependencies [
a0f87f1
]:YutaUra/renovate-changeset-action (YutaUra/renovate-changeset-action)
v0.0.26
Compare Source
Patch Changes
ebf0874
: falsev0.0.25
Compare Source
Patch Changes
e838951
: falsev0.0.24
Compare Source
Patch Changes
1a7d00d
: falsev0.0.23
Compare Source
Patch Changes
304f5a5
: falseactions/create-github-app-token (actions/create-github-app-token)
v1.11.7
Compare Source
v1.11.6
Compare Source
Bug Fixes
v1.11.5
Compare Source
Bug Fixes
v1.11.4
Compare Source
Bug Fixes
v1.11.3
Compare Source
Bug Fixes
v1.11.2
Compare Source
Bug Fixes
actions/setup-node (actions/setup-node)
v4.3.0
Compare Source
v4.2.0
Compare Source
What's Changed
@actions/cache
to^4.0.0
by @priyagupta108 in https://github.com/actions/setup-node/pull/1191New Contributors
Full Changelog: actions/setup-node@v4...v4.2.0
changesets/action (changesets/action)
v1.4.10
Compare Source
Patch Changes
8b16070
Thanks @bluwy! - Use full git email (41898282+github-actions[bot]@​users.noreply.github.com
) for github-actions bot when making commitsint128/wait-for-workflows-action (int128/wait-for-workflows-action)
v1.37.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.36.0...v1.37.0
v1.36.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.35.0...v1.36.0
v1.35.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.34.0...v1.35.0
v1.34.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.33.0...v1.34.0
v1.33.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.32.0...v1.33.0
v1.32.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.31.0...v1.32.0
v1.31.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.30.0...v1.31.0
v1.30.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.29.0...v1.30.0
v1.29.0
Compare Source
What's Changed
Full Changelog: int128/wait-for-workflows-action@v1.28.0...v1.29.0
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. 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 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 throw
ERR_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 check
process.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. 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 nowenabled by default. Use
--no-experimental-detect-module
to 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
.js
or no extension, where the nearest parentpackage.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"
tothe 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) #5656673b5c16684
] - (SEMVER-MINOR) worker: add postMessageToThread (Paolo Insogna) #53682de313b2336
] - (SEMVER-MINOR) module: only emit require(esm) warning under --trace-require-module (Joyee Cheung) [#56194](https://redirect.github.com/nodejs/node/Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.