Guess who's back? π
Node.js Interactive returns at RenderATL 2026.
Join maintainers, contributors, and developers for two days of talks on Node.js performance, security, AI tooling, infrastructure, and the real world challenges of running JavaScript at scale.
See you in Atlanta. Details: https://t.co/LkpGmKXxfa
Are you currently hiring for a role that includes using Node.js? Reply with a link to the opening and any relevant context.
If you're not, we'd appreciate a repost for visibility π
Node.js 26.3.0 is out with a bunch of various fixes, and a new `process.permission.drop()` API (shoutout to @_rafaelgss)
Full changelog and download links: https://t.co/pWguILT1H8
Tomorrow. One hour. Two members of the Node.js Technical Steering Committee.
Matteo Collina (TSC Chair) and Marco Ippolito (TSC & HeroDevs Engineer) join HeroDevs' Javier Perez to talk Node 20 EOL, the path to Node 27 LTS, and how the project is handling a flood of AI-generated CVE reports β plus what to do if you can't migrate off Node 20 yet.
Live Q&A included.
π May 27, 2026 | 11:00 AM EST | Free registration
Register β https://t.co/zd5l2T8Zl0
#NodeJS #OpenSource #EndOfLife #DevSecOps #JavaScript #HeroDevs
Another day, another Node.js release π
Node.js 24.16.0 is out! A few test runner features, `randomUUIDv7`, plus many more bug fixes and small improvements.
Full changelog and download links: https://t.co/rWsnHIlj26
Node.js 26.2.0 is out! β¨
`stream.compose` is now stable, `node:fs` integrates with the new `Temporal` API, and a fair load of bug fixes.
Full changelog and download: https://t.co/VglkTXqgNF
Do you use Node.js on Alpine Linux? While the Node.js project publishes Alpine containers to dockerhub it is currently an "experimental" platform and does not have the same guarantees as other platforms.
We are looking for volunteers to help us bring Alpine to "Tier 2" where it would be built and released through the normal CI process.
If you can help, let us know: https://t.co/AP4BQk6i27
β οΈ Node.js 20 is officially End-of-Life.
Staying on an unsupported version introduces significant security risks, but we know migration takes time. Join members of the Node.js Technical Steering Committee Matteo Collina and Marco Ippolito as we discuss how to navigate this transition safely.
Weβll cover:
β The logic behind the new release cadence leading to Node 27.
β How the project is defending against the surge of AI-generated CVE reports.
β Support options for those unable to migrate off Node 20 immediately.
Donβt leave your production environment to chance. Hear directly from the maintainers.
π May 27 | 11:00 AM EST
π Register for the live session: https://t.co/lHuUeXV2pT
Node.js 26.1.0 is out, with a new `node:ffi` module, `crypto.randomUUIDv7()`, and many more features and bug fixes.
Full changelog and download links: https://t.co/9VpqhfN1gE
Node.js v26.0.0 is out π
Temporal API enabled by default, V8 14.6, Undici 8, and key deprecations as we keep modernizing the platform.
Check it out https://t.co/ASREIY1jM0
Are you currently hiring for a role that includes using Node.js? Reply with a link to the opening and any relevant context.
If you're not, we'd appreciate a repost for visibility π
The 2026 Node.js London Collaboration Summit trip report is officially live! π
We gathered 50+ contributors to discuss the biggest technical shifts coming to the runtime. Hereβs whatβs on the horizon:
ποΈ Versioning Change: Starting with v27, Node.js version numbers will align with the calendar year.
π New Streams API: A more efficient, unified way to handle streams using modern async iterators.
πΎ Node VFS: A proposal for a native Virtual File System (node:vfs) for better SEAs and testing.
βοΈ AI Governance: Evolving our processes to handle the rise of AI-generated code and security reports.
Big thanks to Bloomberg for hosting! π¬π§
Check out the full recap and recordings here:
https://t.co/YPelObdvBj
Are you currently hiring for a role that includes using Node.js? Reply with a link to the opening and any relevant context.
If you're not, we'd appreciate a repost for visibility π
β οΈ Update: The Node.js project's security bug bounty program is being paused.
Reporting remains unchanged, and so does our commitment to security.
More details here: https://t.co/mSJQlPcpk4
The fix has been merged into V8 and can be enabled via `v8_enable_seeded_array_index_hash`. It has been shipped to Node.js v25, v24, v22, and v20 via the March 2026 security release.
Upgrade now to to protect your applications from this vulnerability!
Can a hash be both HashDoS resistant *and* quickly reversible? That's the puzzle we had to tackle in V8 for the March 2026 Node.js security release.
For details, check out our blog post (with the math for the curious!)
For a quick overview, π§΅ below
https://t.co/PsWzHXE33j
With a security release deadline to meet, we interleaved the hash exploration, statistical evaluation, V8 implementation, and performance testing during the development. More details in the blog post.