chore(deps): update node.js to v24 #66
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/node-24.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:
22->24Release Notes
nodejs/node (node)
v24.11.0: 2025-10-28, Version 24.11.0 'Krypton' (LTS), @richardlauCompare Source
Notable Changes
This release marks the transition of Node.js 24.x into Long Term Support (LTS)
with the codename 'Krypton'. It will continue to receive updates through to
the end of April 2028.
Other than updating metadata, such as the
process.releaseobject, to reflectthat the release is LTS, no further changes from Node.js 24.10.0 are included.
Known issue
An issue has been identified in the Node.js 24.x line with
Buffer.allocUnsafeunintentionally returning zero-filled buffers. This API is
documented to return uninitialized memory.
The documented behavior will be restored in the next Node.js 24.x LTS release to bring
it back in line with previous releases. For more information, see
#60423.
v24.10.0: 2025-10-08, Version 24.10.0 (Current), @RafaelGSSCompare Source
Notable Changes
Commits
v24.9.0: 2025-09-25, Version 24.9.0 (Current), @targosCompare Source
Notable Changes
Commits
v24.8.0: 2025-09-10, Version 24.8.0 (Current), @targosCompare Source
Notable Changes
HTTP/2 Network Inspection Support in Node.js
Node.js now supports inspection of HTTP/2 network calls in Chrome DevTools for Node.js.
Usage
Write a
test.jsscript that makes HTTP/2 requests.Run it with these options:
Open
about:inspecton Google Chrome and click onOpen dedicated DevTools for Node.The
Networktab will let you track your HTTP/2 calls.Contributed by Darshan Sen in #59611.
Other Notable Changes
Commits
v24.7.0: 2025-08-27, Version 24.7.0 (Current), @targosCompare Source
Notable Changes
Post-Quantum Cryptography in
node:cryptoOpenSSL 3.5 on 24.x kicked off post-quantum cryptography efforts in Node.js by
allowing use of NIST's post-quantum cryptography standards for future-proofing
applications against quantum computing threats. The following post-quantum
algorithms are now available in
node:crypto:crypto.encapsulate()andcrypto.decapsulate()methods.crypto.sign()andcrypto.verify()methods.Contributed by Filip Skokan in #59259 and #59491.
Modern Algorithms in Web Cryptography API
The second substantial extension to the Web Cryptography API
(
globalThis.crypto.subtle) was recently accepted for incubation by WICG.The following algorithms and methods from this extension are now available in
the Node.js Web Cryptography API implementation:
subtle.getPublicKey()SubtleCrypto.supports()Contributed by Filip Skokan in #59365, #59569, #59461, and #59539.
Node.js execution argument support in single executable applications
The single executable application configuration now supports additional fields
to specify Node.js execution arguments and control how they can be extended when
the application is run.
execArgvtakes an array of strings for the execution arguments to be used.execArgvExtensiontakes one of the following values:"none": No additional execution arguments are allowed."cli": Additional execution arguments can be provided via a special command-line flag--node-options="--flag1 --flag2=value"at run time."env"(default): Additional execution arguments can be provided via theNODE_OPTIONSenvironment variable at run time.For example, with the following configuration:
If the generated single executable application is named
sea, then running:Would be equivalent to running:
Contributed by Joyee Cheung in #59314 and #59560.
Root certificates updated to NSS 3.114
Certificates added:
Certificates removed:
Other Notable Changes
Commits
v24.6.0: 2025-08-14, Version 24.6.0 (Current), @RafaelGSSCompare Source
Notable Changes
Commits
v24.5.0: 2025-07-31, Version 24.5.0 (Current), @aduh95Compare Source
Notable Changes
Upgrade to OpenSSL 3.5
This release is distributed with OpenSSL 3.5.1, following the announcement that
OpenSSL 3.5 will be supported until April 2030, while Node.js 24 will be
supported until April 2028. Read more about OpenSSL support in their blog post:
https://openssl-library.org/post/2025-02-20-openssl-3.5-lts/.
Contributed by Richard Lau in #58100.
Unflag
--experimental-wasm-modulesNode.js supports both source phase imports and instance phase imports to WebAssembly
modules and for WASM imports to JavaScript, in line with the current Phase 3
WebAssembly ESM Integration proposal.
The implementation and the specification are still subject to change.
Contributed by Guy Bedford in #57038.
Built-in proxy support in
request()andAgentnode:httpandnode:httpsnow support proxies. WhenNODE_USE_ENV_PROXYis set to
1, the default global agent would parse thehttp_proxy/HTTP_PROXY,https_proxy/HTTPS_PROXY,no_proxy/NO_PROXYsettings from theenvironment variables, and proxy the requests sent through the built-in http/https
client accordingly.
To use global proxy support from the command line:
In addition,
http.Agentandhttps.Agentnow support the customproxyEnvoptions.For reference,
fetch()already supportsNODE_USE_ENV_PROXYas of Node.js 24.0.0.Contributed by Joyee Cheung in #58980.
Add
setDefaultCACertificates()tonode:tlsThis API allows dynamically configuring CA certificates that will be used by the
Node.js TLS clients by default.
Once called, the provided certificates will become the default CA certificate list
returned by
tls.getCACertificates('default')and used by TLS connections thatdon't specify their own CA certificates.
To add system CA certificates to the default bundle (which includes the Mozilla
CA certificates):
Contributed by Joyee Cheung in #58822.
Other notable changes
Commits
v24.4.1: 2025-07-15, Version 24.4.1 (Current), @RafaelGSSCompare Source
This is a security release.
Notable Changes
Commits
v24.4.0: 2025-07-09, Version 24.4.0 (Current), @RafaelGSSCompare Source
Notable Changes
Commits
v24.3.0: 2025-06-24, Version 24.3.0 (Current), @RafaelGSSCompare Source
Notable Changes
Commits
v24.2.0: 2025-06-09, Version 24.2.0 (Current), @aduh95Compare Source
Notable Changes
Remove support for HTTP/2 priority signaling
The support for priority signaling has been removed in nghttp2, following its
deprecation in the RFC 9113.
As a consequence of this, priority signaling is deprecated on all release lines of Node.js,
and removed from Node.js 24 so we can include latest updates from nghttp2.
Contributed by Matteo Collina and Antoine du Hamel in
#58293.
import.meta.mainis now availableBoolean value available in ECMAScript modules, which can be used to detect
whether the current module was the entry point of the current process.
Contributed by Joe and Antoine du Hamel in
#57804.
Other Notable Changes
Commits
v24.1.0: 2025-05-21, Version 24.1.0 (Current), @aduh95Compare Source
Notable Changes
Commits
v24.0.2: 2025-05-14, Version 24.0.2 (Current), @RafaelGSSCompare Source
This is a security release.
Notable Changes
Commits
v24.0.1: 2025-05-08, Version 24.0.1 (Current), @aduh95Compare Source
Notable Changes
Commits
v24.0.0: 2025-05-06, Version 24.0.0 (Current), @RafaelGSS and @juanarbolCompare Source
We’re excited to announce the release of Node.js 24! This release brings
several significant updates, including the upgrade of the V8 JavaScript
engine to version 13.6 and npm to version 11. Starting with
Node.js 24, support for MSVC has been removed, and ClangCL is now required
to compile Node.js on Windows. The
AsyncLocalStorageAPI now usesAsyncContextFrameby default, andURLPatternis available globally.These changes, along with many other improvements, continue to push the
platform forward.
As a reminder, Node.js 24 will enter long-term support (LTS) in October,
but until then, it will be the "Current" release for the next six months.
We encourage you to explore the new features and benefits offered by this
latest release and evaluate their potential impact on your applications.
Notable Changes
V8 13.6
The V8 engine is updated to version 13.6, which includes several new
JavaScript features:
Float16ArrayRegExp.escapeError.isErrorThe V8 update was a contribution by Michaël Zasso in #58070.
npm 11
Node.js 24 comes with npm 11, which includes several improvements and new
features. This update brings enhanced performance, improved security features,
and better compatibility with modern JavaScript packages.
The npm update was a contribution by the npm team in #56274.
AsyncLocalStoragedefaults toAsyncContextFrameAsyncLocalStoragenow usesAsyncContextFrameby default, which provides amore efficient implementation of asynchronous context tracking.
This change improves performance and makes the API more robust for advanced
use cases.
This change was a contribution by Stephen Belanger in #55552.
URLPatternas a globalThe
URLPatternAPI is now exposed on the global object, making it easier to use without
explicit imports. This API provides a powerful pattern matching system for URLs,
similar to how regular expressions work for strings.
This feature was a contribution by Jonas Badalič in #56950.
Permission Model Improvements
The experimental Permission Model introduced in Node.js 20 has been improved,
and the flag has been changed from
--experimental-permissionto simply--permission, indicating its increasing stability and readiness for broaderadoption.
This change was a contribution by Rafael Gonzaga in #56240.
Test Runner Enhancements
The test runner module now automatically waits for subtests to finish,
eliminating the need to manually await test promises. This makes writing tests
more intuitive and reduces common errors related to unhandled promises.
The test runner improvements were contributions by Colin Ihrig in #56664.
Undici 7
Node.js 24 includes Undici 7, which brings numerous improvements to the
HTTP client capabilities, including better performance and support for newer
HTTP features.
Deprecations and Removals
Several APIs have been deprecated or removed in this release:
url.parse()- use the WHATWG URL API instead (#55017)tls.createSecurePair(#57361)SlowBuffer(#55175)new(#55718)argstospawnandexecFilein child_process (#57199)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.