Node.js — Node.js 22 is now available!
We're excited to announce the release of Node.js 22! Highlights include require()ing ES modules, a WebSocket client, updates of the V8 JavaScript engine, and more! Node.js 22 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 th
Node.js — Trip report: Node.js collaboration summit (2024 London)
About twice per year, Node.js contributors and community members get together in an unconference called the Node.js collaboration summit. At the summit, we share knowledge about the project and the ecosystem, brainstorm solutions to technical and non-technical issues, make progress in decision-making discussions, and push forward new initiatives. The first collaboration summit of 2024 was held on
Node.js — Node v21.0.0 (Current)
2023-10-17, Version 21.0.0 (Current), @RafaelGSS and @targos We're excited to announce the release of Node.js 21! Highlights include updates of the V8 JavaScript engine to 11.8, stable fetch and WebStreams, a new experimental flag to change the interpretation of ambiguous code from CommonJS to ES modules (--experimental-default-type), many updates to our test runner, and more! Node.js 21 will repl
Node.js — Node v20.0.0 (Current)
Notable Changes Permission Model Node.js now has an experimental feature called the Permission Model. It allows developers to restrict access to specific resources during program execution, such as file system operations, child process spawning, and worker thread creation. The API exists behind a flag --experimental-permission which when enabled will restrict access to all available permissions. B
Node.js — Bringing forward the End-of-Life Date for Node.js 16
Changing the End-of-Life Date for Node.js 16 to September 11th, 2023 Summary We are moving the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on September 11th, 2023. Why? When we put together Node.js 16 the hope was that we would be able to include OpenSSL 3. Unfortunately, the timing of the releases did not allow that to be possible, and we re
Node.js — Node v17.0.1 (Current)
Notable Changes Fixed distribution for native addon builds This release fixes an issue introduced in Node.js v17.0.0, where some V8 headers were missing from the distributed tarball, making it impossible to build native addons. These headers are now included. #40526 Fixed stream issues Fixed a regression in stream.promises.pipeline, which was introduced in version 16.10.0, is fixed. It is now poss
Web Streams API | Node.js v22.0.0 Documentation
An implementation of the WHATWG Streams Standard. Overview# The WHATWG Streams Standard (or "web streams") defines an API for handling streaming data. It is similar to the Node.js Streams API but emerged later and has become the "standard" API for streaming data across many JavaScript environments. There are three primary types of objects: ReadableStream - Represents a source of streaming data. Wr
Node.js — Node v16.0.0 (Current)
Notable Changes Deprecations and Removals (SEMVER-MAJOR) fs: remove permissive rmdir recursive (Antoine du Hamel) #37216 (SEMVER-MAJOR) fs: runtime deprecate rmdir recursive option (Antoine du Hamel) #37302 (SEMVER-MAJOR) lib: runtime deprecate access to process.binding('http_parser') (James M Snell) #37813 (SEMVER-MAJOR) lib: runtime deprecate access to process.binding('url') (James M Snell) #377
Node.js — January 2021 Security Releases
(Update 4-Jan-2021) Security releases available Updates are now available for v10,x, v12.x, v14.x and v15.x Node.js release lines for the following issues. In addition to the vulnerabilities listed below, these releases also include an update to npm in order to resolve an issue that was reported against npm by security scanners even though it was not vulnerable. use-after-free in TLSWrap (High) (C
Node.js — Node v10.7.0 (Current)
Notable Changes console: The console.timeLog() method has been implemented. #21312 deps: Upgrade to libuv 1.22.0. #21731 Upgrade to ICU 62.1 (Unicode 11, CLDR 33.1). #21728 http: Added support for passing both timeout and agent options to http.request. #21204 inspector: Expose the original console API in require('inspector').console. #21659 napi: Added experimental support for functions dealing wi
Node v8.8.0 (Current) | Node.js
Notable Changes crypto: expose ECDH class #8188 http2: http2 is now exposed by default without the need for a flag #15685 a new environment variable NODE_NO_HTTP2 has been added to allow userland http2 to be required #15685 support has been added for generic Duplex streams #16269 module: resolve and instantiate loader pipeline hooks have been added to the ESM lifecycle #15445 zlib: CVE-2017-14919
Node v8.2.0 (Current) | Node.js
Big thanks to @addaleax who prepared the vast majority of this release. Notable changes Async Hooks Multiple improvements to Promise support in async_hooks have been made. Build The compiler version requirement to build Node with GCC has been raised to GCC 4.9.4. [820b011ed6] #13466 Cluster Users now have more fine-grained control over the inspector port used by individual cluster workers. Previou
Node v8.1.4 (Current) | Node.js
Notable changes build: Disable V8 snapshots - The hashseed embedded in the snapshot is currently the same for all runs of the binary. This opens node up to collision attacks which could result in a Denial of Service. We have temporarily disabled snapshots until a more robust solution is found (Ali Ijaz Sheikh) deps: CVE-2017-1000381 - The c-ares function ares_parse_naptr_reply(), which is used for
Security updates for all active release lines, July 2017 | Node.js
Security updates for all active release lines, July 2017 (Update 10-August-2017) Snapshots Re-enabled on 8.3.0 The vulnerability has been patched upstream and snapshots have been re-enabled in 8.3.0 Expect a backport and update with the next release of 6.x Download Node.js v8 (Current) (Update 11-July-2017) Security releases available Summary Updates are now available for all active Node.js releas
Node v8.0.0 (Current) | Node.js
The next major release of Node.js brings a range of significant changes and additions, far too many for us to cover adequately in a blog post such as this. This article contains a summary of the most significant changes and features. Say hello to npm version 5.0.0 npm, Inc. recently announced the release of version 5.0.0 of the npm client and we are happy to include this significant new version wi
Node v7.5.0 (Current) | Node.js
Notable changes crypto: ability to select cert store at runtime (Adam Majer) #8334 Use system CAs instead of using bundled ones (Adam Majer) #8334 deps: upgrade npm to 4.1.2 (Kat Marchán) #11020 upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) #11021 doc: add basic documentation for WHATWG URL API (James M Snell) #10620 process: add NODE_NO_WARNINGS environment variable (cjihrig) #10842 url: allo
Node.js — OpenSSL update, 1.0.2k
(Update 1-February-2017) Releases available Updates are now available for all active Node.js release lines. The following releases are bundled with OpenSSL 1.0.2k: Node.js 7.5.0 (Current) Node.js 6.9.5 (LTS "Boron") Node.js 4.7.3 (LTS "Argon") While this is not a critical update, all users of these release lines should upgrade at their earliest convenience. Original post is included below The Open
Node.js — Node v7.3.0 (Current)
Notable changes buffer: buffer.fill() now works properly for the UCS2 encoding on Big-Endian machines. (Anna Henningsen) #9837 cluster: disconnect() now returns a reference to the disconnected worker. (Sean Villars) #10019 crypto: The built-in list of Well-Known CAs (Certificate Authorities) can now be extended via a NODE_EXTRA_CA_CERTS environment variable. (Sam Roberts) #9139 http: Remove stale
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Index of /download/v8-canary/
Diag WG Update - Many new tools, phasing out some old ones | Node.js