Update Node.js to v21 #260
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/node-21.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-bullseye->21.7.3-bullseyeRelease Notes
nodejs/node (node)
v21.7.3: 2024-04-10, Version 21.7.3 (Current), @RafaelGSSCompare Source
This is a security release.
Notable Changes
child_process.spawnwithout shell option enabled on WindowsCommits
v21.7.2: 2024-04-03, Version 21.7.2 (Current), @RafaelGSS prepared by @marco-ippolitoCompare Source
This is a security release.
Notable changes
Commits
v21.7.1: 2024-03-08, Version 21.7.1 (Current), @targosCompare Source
Notable Changes
This release reverts #51389, which
landed in Node.js 21.7.0. It is a documented feature that
t.after()hooks arerun even if a test has no subtests. The hook can be used to clean up the test
itself.
Commits
v21.7.0: 2024-03-06, Version 21.7.0 (Current), @RafaelGSS prepared by @marco-ippolitoCompare Source
Text Styling
util.styleText(format, text): This function returns a formatted text considering theformatpassed.A new API has been created to format text based on
util.inspect.colors, enabling you to style text in different colors (such as red, blue, ...) and emphasis (italic, bold, ...).Contributed by Rafael Gonzaga and Hemanth HM in #51850.
Loading and parsing environment variables
process.loadEnvFile(path):.envfile. If no path is specified, it automatically loads the .env file in the current directory. Example:process.loadEnvFile().process.loadEnvFile('./development.env').util.parseEnv(content):require('node:util').parseEnv('HELLO=world').Contributed by Yagiz Nizipli in #51476
Support for multi-line values for
.envfileNode.js 21.7.0 will now support multi-line values in the .env file:
Contributed by Ilyas Shabi #51289
sea: support embedding assets
Users can now include assets by adding a key-path dictionary
to the configuration as the
assetsfield. At build time, Node.jswould read the assets from the specified paths and bundle them into
the preparation blob. In the generated executable, users can retrieve
the assets using the
sea.getAsset()andsea.getAssetAsBlob()API.The single-executable application can access the assets as follows:
Contributed by Joyee Cheung in #50960
vm: support using the default loader to handle dynamic import()
This patch adds support for using
vm.constants.USE_MAIN_CONTEXT_DEFAULT_LOADERas theimportModuleDynamicallyoption in all vm APIs that take this option exceptvm.SourceTextModule. This allows users to have a shortcut to support dynamicimport()in the compiled code without missing the compilation cache if they don't need customization of the loading process. We emit an experimental warning when theimport()is actually handled by the default loader through this option instead of requiring--experimental-vm-modules.Contributed by Joyee Cheung in #51244
crypto: implement crypto.hash()
This patch introduces a helper crypto.hash() that computes
a digest from the input at one shot. This can be 1.2-2x faster
than the object-based createHash() for smaller inputs (<= 5MB)
that are readily available (not streamed) and incur less memory
overhead since no intermediate objects will be created.
Contributed by Joyee Cheung in #51044
Other Notable Changes
Commits
v21.6.2: 2024-02-14, Version 21.6.2 (Current), @RafaelGSSCompare Source
Notable changes
This is a security release.
Notable changes
Commits
v21.6.1: 2024-01-22, Version 21.6.1 (Current), @RafaelGSSCompare Source
Notable Changes
This release fixes a bug in
undiciusing WebStreamsCommits
v21.6.0: 2024-01-15, Version 21.6.0 (Current), @RafaelGSSCompare Source
New connection attempt events
Three new events were added in the
net.createConnectionflow:connectionAttempt: Emitted when a new connection attempt is established. In case of Happy Eyeballs, this might emitted multiple times.connectionAttemptFailed: Emitted when a connection attempt failed. In case of Happy Eyeballs, this might emitted multiple times.connectionAttemptTimeout: Emitted when a connection attempt timed out. In case of Happy Eyeballs, this will not be emitted for the last attempt. This is not emitted at all if Happy Eyeballs is not used.Additionally, a previous bug has been fixed where a new connection attempt could have been started after a previous one failed and after the connection was destroyed by the user.
This led to a failed assertion.
Contributed by Paolo Insogna in #51045.
Changes to the Permission Model
Node.js 21.6.0 comes with several fixes for the experimental permission model and two new semver-minor commits.
We're adding a new flag
--allow-addonsto enable addon usage when using the Permission Model.Contributed by Rafael Gonzaga in #51183
And relative paths are now supported through the
--allow-fs-*flags.Therefore, with this release one can use:
To give only read access to the entrypoint of the application.
Contributed by Rafael Gonzaga and Carlos Espa in #50758
Support configurable snapshot through
--build-snapshot-configflagWe are adding a new flag
--build-snapshot-configto configure snapshots through a custom JSON configuration file.When using this flag, additional script files provided on the command line will
not be executed and instead be interpreted as regular command line arguments.
These changes were contributed by Joyee Cheung and Anna Henningsen in #50453
Other Notable Changes
Commits
v21.5.0: 2023-12-19, Version 21.5.0 (Current), @RafaelGSSCompare Source
Notable Changes
Deprecations
Commits
v21.4.0: 2023-12-05, Version 21.4.0 (Current), @targosCompare Source
Notable Changes
This release fixes a regression introduced in v21.3.0 that caused the
fs.writeFileSyncmethod to throw when called with
'utf8'encoding, no flag option, and if the target file didn't exist yet.Commits
v21.3.0: 2023-11-30, Version 21.3.0 (Current), @RafaelGSSCompare Source
Notable Changes
New
--disable-warningflagThis version adds a new
--disable-warningoption that allows users to disable specific warnings either by code(i.e. DEP0025) or type (i.e. DeprecationWarning, ExperimentalWarning).
This option works alongside existing
--warningsand--no-warnings.For example, the following script will not emit DEP0025
require('node:sys')when executed withnode --disable-warning=DEP0025:Contributed by Ethan-Arrowood in #50661
Update Root Certificates to NSS 3.95
This is the certdata.txt from NSS 3.95, released on 2023-11-16.
This is the version of NSS that will ship in Firefox 121 on
2023-12-19.
Certificates added:
Certificates removed:
A626340Fast fs.writeFileSync with UTF-8 Strings
Enhanced writeFileSync functionality by implementing a highly efficient fast path primarily in C++ for UTF8-encoded string data.
Additionally, optimized the
appendFileSyncmethod by leveraging the improvedwriteFileSyncfunctionality.For simplicity and performance considerations, the current implementation supports only string data,
as benchmark results raise concerns about the efficacy of using Buffer for this purpose.
Future optimizations and expansions may be explored, but for now, the focus is on maximizing efficiency for string data operations.
Contributed by CanadaHonk in #49884.
Other Notable Changes
Commits
v21.2.0: 2023-11-14, Version 21.2.0 (Current), @targosCompare Source
Notable Changes
Commits
v21.1.0: 2023-10-24, Version 21.1.0 (Current), @targosCompare Source
Notable Changes
Automatically detect and run ESM syntax
The new flag
--experimental-detect-modulecan be used to automatically runES modules when their syntax can be detected. For “ambiguous” files, which are
.jsor extensionless files with nopackage.jsonwith atypefield, Node.jswill parse the file to detect ES module syntax; if found, it will run the file
as an ES module, otherwise it will run the file as a CommonJS module.
The same applies to string input via
--evalorSTDIN.We hope to make detection enabled by default in a future version of Node.js.
Detection increases startup time, so we encourage everyone — especially package
authors — to add a
typefield topackage.json, even for the default"type": "commonjs". The presence of atypefield, or explicit extensionssuch as
.mjsor.cjs, will opt out of detection.Contributed by Geoffrey Booth in #50096.
Other Notable Changes
Commits
v21.0.0: 2023-10-17, Version 21.0.0 (Current), @RafaelGSS and @targosCompare Source
We're excited to announce the release of Node.js 21! Highlights include updates of the V8 JavaScript engine to 11.8,
stable
fetchandWebStreams, a new experimental flag to change the interpretation of ambiguous codefrom CommonJS to ES modules (
--experimental-default-type), many updates to our test runner, and more!Node.js 21 will replace Node.js 20 as our ‘Current’ release line when Node.js 20 enters long-term support (LTS) later this month.
As per the release schedule, Node.js 21 will be ‘Current' release for the next 6 months, until April 2024.
Other Notable Changes
Semver-Major Commits
Semver-Minor Commits
Semver-Patch 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 this update again.
This PR has been generated by Renovate Bot.
baaf9cee98to69a160e1f769a160e1f7tob739f42817b739f42817to6b22e897236b22e89723to7b8b1ae06e7b8b1ae06eto41c0c07e0f41c0c07e0fto74f542bfa774f542bfa7to0961ed421d0961ed421dtoa1448d8f1ea1448d8f1eto228fc50ed5228fc50ed5to8875becb6c8875becb6cto9a910b7e8d9a910b7e8dto69859a5e6369859a5e63to22137bc40922137bc409toc629790c9fc629790c9ftofe74dff98ffe74dff98fto90defe89dc90defe89dcto2a297f107e2a297f107eto7edf44dfd47edf44dfd4toacce1b784facce1b784fto8d8cded2b68d8cded2b6to6bce7718eb6bce7718ebto6949d27ab86949d27ab8to397c26293b397c26293bto5ea555819c5ea555819cto48948ba1e248948ba1e2toed3a849274ed3a849274todbdd16cf9cdbdd16cf9cto77bd0b718177bd0b7181to03c20b4cf803c20b4cf8to78b54b6f9578b54b6f95to747038199d747038199dto5e699e61c25e699e61c2tof6b9f24e20f6b9f24e20to6ed48ba14b6ed48ba14bto6e03022bd06e03022bd0to824def9a0f824def9a0fto11375c695a11375c695ato30b630647430b6306474to676d04f763676d04f763todfecc6ecf44aa4a76923to35e98cb75c35e98cb75cto7503da5aa27503da5aa2tof4c2e933f5f4c2e933f5tob4db648284b4db648284toefd5663667efd5663667to3b4b678e6f3b4b678e6fto6187e930666187e93066to885a522c1b885a522c1bto7cbd5d41157cbd5d4115to1ed0b0db901ed0b0db90to733fb3c8db733fb3c8dbto2b625683772b62568377toe8e4b52d80e8e4b52d80to8e771403978e77140397to9d7b325bf29d7b325bf2to9add295a5e9add295a5eto24ced1200d24ced1200dtoa815cc6409a815cc6409to793719f305793719f305to406f7e68a9406f7e68a9toba4109b583ba4109b583to85436a50a685436a50a6to6ffe9c7c166ffe9c7c16tof5b2052b59f5b2052b59to6f25bb68f36f25bb68f3to136ba8bd7b136ba8bd7btoa753cc2b38a753cc2b38to00f7dbbbdc00f7dbbbdctobb6e508a1dbb6e508a1dtoa672b02478a672b02478to9ccec9c43f9ccec9c43fto92d87a6deb92d87a6debto44e8ead2c744e8ead2c7tof8618e96a4f8618e96a4toe4fa877ad8e4fa877ad8toa9cfe3d790a9cfe3d790to8e59e848778e59e84877tof562a85888f562a85888to07924340f607924340f6to79e946b70d79e946b70dto296a47951d296a47951dtoaefc101d02aefc101d02tof90948455cf90948455ctobfb0e2d610bfb0e2d610tocc368299dbcc368299dbtoee2a00eb00ee2a00eb00to4f0f3a9e624f0f3a9e62to0661d0a20c0661d0a20ctod96a14da25d96a14da25toc49a249cfdc49a249cfdto9d600c6ed5Update Node.js to v21to Update node Docker tag to v21Update node Docker tag to v21to Update Node.js to v219d600c6ed5to24865d8daa24865d8daato63a67593cf63a67593cftoc68e1cf309c68e1cf309to6f00843f806f00843f80tofaddd2b6e1faddd2b6e1to5892dd3c445892dd3c44to0682c7cbed0682c7cbedto942f1642c8942f1642c8toc2e198d446Checkout
From your project repository, check out a new branch and test the changes.