The @nodejs.org is nearing consensus on shifting to annual releases, with a blog post coming soon 🥳
I have a nitpick on naming the prelease channel "Alpha"
I've suggested some alternatives, and made a case for why "preview" might be a better fit.
WDYT? 🤔
Details: github.com/nodejs/nodej...
Announcing the @nodejs.org LTS Upgrade and Modernization Program! 🚀
We're helping enterprises move safely off end-of-life Node.js versions to reduce security risks with our partnerNodeSource.
Modern Node.js is safer Node.js. Details:
openjsf.org/blog/nodejs-...
Via Node Weekly:
💡 A cute side effect of the change will be the latest LTS Node version will match the year. Node 28 will go LTS in 2028, and so on.
nodeweekly.com/issues/614
Node.js v22.22.1 is out 🔥
Release notes 👇
nodejs.org/en/blog/rele...
Node.js v20.20.1 is out 🎉
This is the last planned release before v20 goes End-of-Life ❗
Release notes 👇
nodejs.org/en/blog/rele...
JavaScript's date object has been tricky for years, but that is changing.
The NEW Temporal API brings,
🌍 Easily handle time zones
📆 Precise date math
🕒 Parse ISO strings without errors
⌛ Durations, date ranges, and more.
Start experimenting 👇
developer.mozilla.org/en-US/docs/...
Fixed up some perf issues and benchmark bugs in the new-streams reference impl ... some highlights running comparisons on @nodejs.org @deno.land and @bun.sh ... note each column is just looking at the one runtime, not comparing runtimes against each other ...
☕ Something's brewing for @nodejs.org releases starting with 27.x. Official announcement coming soon!
👀 Sneak peek: github.com/nodejs/nodej...
After implementing web streams in multiple runtimes, supporting them for years, talking with other implementers, dealing with issues... I think it's well past time we talked about something better blog.cloudflare.com/a-better-web...
Node.js release day! @ruyadorno.com and I just released Node.js 24.14.0 and 25.7.0, full changelog and download links at nodejs.org/en/blog/rele... and nodejs.org/en/blog/rele...
🎉 We’re thrilled to welcome @socket.dev as our newest Silver member.
Socket is doing critical work to secure the JavaScript ecosystem by helping developers identify and prevent supply chain risks. We're excited to collaborate and make open source safer for everyone! 🛡️💻
openjsf.org/blog/socket-...
✨ Keep up to date with @nodejs.org by watching the #Nodejs #Release Working Group's last meeting on YouTube!
www.youtube.com/watch?v=ulMh...
I just published the January report for open source software packages for Linux on #IBMZ and #LinuxONE 🐧
The team tested nearly two dozen projects, including doxygen, Elastic Logstash, and PHP 🥳
Full report: community.ibm.com/community/us... #mainframe
Node.js patch release day! Full changelog and download links at nodejs.org/en/blog/rele... and nodejs.org/en/blog/rele...
Want to make an impact? Join the OpenJS Foundation. Fund the projects you rely on. Contribute engineer time where it matters.
It took a while, but the State of JS 2025 survey results are now live! 2025.stateofjs.com/en-US
Thanks to @danielroe.dev for contributing the conclusion.
We released version 1.2 of our GitHub Actions service for IBM Z and Power 🎉 including improvements to Python support, so you can now use the IBM fork (until it's accepted upstream) of python-versions to specify versions: community.ibm.com/community/us...
I think I figured out what's going on. Here is another blog post about tinkering with Node.js Core on ARM64 Windows (and tips about reducing the wait time on Windows) joyeecheung.github.io/blog/2026/01...
nvm.sh users: please upgrade to github.com/nvm-sh/nvm/r... if you're using `wget` on your system, to fix a medium vulnerability (github.com/nvm-sh/nvm/s...).
🚨 Node.js assessment of the recent OpenSSL Security Release
TL;DR: We'll update OpenSSL versions through a regular release process.
nodejs.org/en/blog/vuln...
I love how the answer to the title of this article is "they don't"
"Why Costco Still Relies On IBM Computers From The '80s"
www.bgr.com/2079471/why-...
The new Power 11 servers are so shiny ✨ I was able to meet my first one at IBM TechXchange 2025 back in October.
(I work on IBM Z, not Power)
⚠️ The Node.js Project now requires a HackerOne Signal score of 1.0 or higher to submit vulnerability reports. This will help our team streamline reports and support effective security reviews.
nodejs.org/en/blog/anno...
How did we do at the end of 2025 as far as testing our current collection of open source software packages for Linux on #IBMZ and #LinuxONE?
It was a strong finish! The team worked on over two dozen packages, including cAdvisor, PostgreSQL, and SPIRE.
Full report: community.ibm.com/community/us...
State of WebAssembly (Wasm) - recap events of 2025 and preview what 2026 can bring.
platform.uno/blog/the-sta...
This release contains a bunch of PRs I recently submitted to mark features I contributed to as stable/release candidate. Here is a thread about them 🧵:
Node.js v25.4.0 is out! 💚
• require(esm) now stable and a new CLI flag: --require-module
• http setGlobalProxyFromEnv() added
• Multiple APIs promoted to stable (heapsnapshot, build snapshot, v8.queryObjects)
• Root CAs updated to NSS 3.117
More in: nodejs.org/en/blog/rele...
Today the Temporal proposal has entered the stable stream shipping Chrome 144. This opens the gates for attaining Stage 4 at TC39.
That means tonight I will be purchasing a supply of champagne in preparation.
It’s been a long journey and so very worthwhile!
Today, we published a security release for @nodejs.org that fixes a critical bug affecting virtually every production Node.js app.
If you use React Server Components, Next.js, or ANY APM tool (Datadog, New Relic, OpenTelemetry), your app could be vulnerable to DoS attacks.
👇
