NodeConf EU is back in Bologna, Italy and it's going to be special 🇮🇹 Great talks, better people, and the kind of hallway track you can't replicate online. Blind tickets? Already gone. CFP open. Regular tickets moving. Join us: www.nodeconf.eu

Trust me, @nodeland.dev and I talked A LOT about that. I helped kill @expressjs.bsky.social usage at my work, but the numbers keep going up year over year. We need real transition plans, and that takes *work* that is not glamorous.

For those who build or redistribute Node.js - as the V8 implementation of temporal depends on temporal_rs, this also means starting from v26 building Node.js fully requires a Rust toolchain. See github.com/nodejs/node/...

The hidden gem is that @nodejs.org majors and LTS cycles got WAY easier to understand: 2026 -> v26 2027 -> v27 2028 -> v28 ... Aall of them go LTS for 18 months meaning each major is supported for 2 years. The new graphic tells the best story here: nodejs.org/en/blog/anno...

The Axios npm compromise was a social engineering attack — not a leaked password, not a stolen key. The attacker hijacked the maintainer's *live browser session*. As far as npm was concerned, they *were* the maintainer. This exposes a dangerous gap in how we think about supply chain security. 👇

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. Big thanks to Bloomberg for hosting! 🇬🇧 Check out the full recap and recordings here: https://bit.ly/3OHPLmz

Most teams think autoscaling is solved. Set a CPU threshold. Let Kubernetes do the rest. Then a 3-min spike hits, your pods take 2 min to boot, and the party is over before they show up. New episode of The Node (and more) Banter drops May 6th. 🧵

20x lower median latency than HPA. 6x lower than KEDA. 17x fewer failed requests than HPA. 9x fewer than KEDA. Same app. Same cluster. Same metric. The only thing we changed was the autoscaler. 🧵

Medusa is a flexible open source commerce platform for Node.js. It pushes you toward a multi-app architecture from day one: - backend API - admin UI - storefront - image optimizer - shared env vars - public + internal URLs The repo sprawl problem starts here.

Why is Claude Code so good? It's not just the model. It's that the harness runs in the same host where the code executes. Same filesystem. Same process tree. Same state. That co-location is the feature. And it's exactly what production agents lose.

You can use nvm to kick the tires on `node:ffi`! NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/nightly nvm install 26

Do not unleash your AI-powered bot into people's GitHub repos without asking first. If you do that on any of the repos I maintain, your bot is likely to get banned. (I've already banned a few).

🔥 NEW BANTER: "AI Agents, Kubernetes, and the Sandbox That Made It Possible" Most teams building AI agents treat Kubernetes like it is optional. Until someone asks how to scale it. Or govern it. @lucamaraschi and I did a full launch week debrief. 📅 April 22nd 🔗 streamyard.com/watch/9n4cF3...

Along with the blog post there's a recording of the interview. Listen to the full interview OR the last 10 minutes (linked). www.youtube.com/watch?v=ZbWx...

I’m so stocked that Codemotion made me as a Magic card. 🥹 See you tomorrow at conferences.codemotion.com/roma/

Another awesome post by @nodeland.dev This express 100% my vision for AI-assisted coding.

Readers spotted that compression was not applied consistently in our React SSR benchmarks. TanStack Start had it disabled while the others had it on. We disabled compression everywhere and re-ran the tests. Here are the corrected results.

🔥 NEW BANTER: "Node.js VFS: Unlocking Dynamic Code, Testing, and Multi-Tenancy" 🔗 streamyard.com/watch/qjiaVX...

I’m stoked by the amount of private feedbacks I’m receiving for leading the AI contributions discussion so far. Thank you all ❤️.

We just launched @Platformatic World 🚀 It brings durable workflow orchestration to Kubernetes with full version safety. If you use @WorkflowDevKit, your workflows now run on your own cluster with the same guarantees you get on @Vercel.

Hey I wrote a personal blog post... www.jasnell.me/posts/ai-in-os

Next.js 16.2 • Up to ~60% faster rendering • Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup • Server Function 𝚍𝚎𝚟 logging • Redesigned error page • Better hydration errors • 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay nextjs.org/blog/next-16-2

🧵 I wrote almost 19,000 lines of code for a Virtual File System in @nodejs.org core using Claude Code. It started over Christmas and has been refined over almost three months of review. A collaborator challenged whether AI-assisted contributions can meet the DCO requirements. Here's what happened:

Now that I’m using both Claude and Codex daily, I’m seeing that Claude tries to “cheat” more often, eg deleting a failing test. What’s your experience?

Your coding agent keeps making the same mistakes? I built a fix. Introducing pi-self-learning: a pi extension that gives your coding agent actual memory. It extracts what went wrong after each task, scores learning by frequency/recency, and automatically injects them into context. 🧵 👇

.@nodejs has always been about I/O. Streams, buffers, sockets, files. But there's a gap that has bugged me for years: you can't virtualize the filesystem. You can't import a module that only exists in memory. You can't bundle assets into a Single Executable without patching half of core. 👇

Here is a fun one. Somebody is using an AI to post a message (relavant, but stating the obvious) on ALL issues on one of the orgs I’m managing on github. The net result is literally a DoS on maintainers, because he is making any kind of notification management useless. Shall I ban?

A number of years ago, @nodeland.dev and I did a keynote at Node.js Interactive in Vancouver on the theme of Open Source is Art. Nearform created some popular swag T-shirts based on the theme. (It was actually Cian O Maidin's talk but he couldn't make it so Matteo and I delivered it...

🔥 NEW BANTER: "Why Node.js Is the Critical Enabler for AI Applications" Everyone's building AI apps. Almost nobody's talking about what runs them. Hint: it's not Python. @lucamaraschi and I make the case for Node.js as the backbone of production AI. 📅 March 18th

This NodeWeekly release is the best nodeweekly.. or at least the one with the best image! nodeweekly.com/issues/615

🎯 After years of building with Node.js, I've organized my hard-won knowledge into skills: a collection of best practices, workflows, and deep expertise my AI assistant uses to write code to my standard. No more repeating myself on every code review. 👇

Grammarly uses AI trained on my talks to review articles. Especially my new articles. I find this flattering and amusing... but also a bit worried for the future. What would you do if they trained an AI after your style?

Are you hosting Next.js on K8s? Your Next.js image optimization is quietly killing your frontend performance. We (@platformatic) just shipped a way to fix it without changing a single line of your app code 🧵

🔥 NEW BANTER: Kubernetes Finally Gets Vercel-Style Deployment Safety

💻 Take your Node.js to the next level! Hands-on workshop with @nodeland.dev: learn async patterns, advanced caching, worker threads & observability to scale high-performance apps. Limited seats! 🎟️ london.cityjsconf.org/

We just shipped something big: Skew Protection for your Kubernetes apps, built right into the @platformatic Intelligent Command Center (ICC). Think @Vercel-style deployment safety, but running in your own K8s cluster. No migration needed. Here's why it matters. 🧵

We just shipped something big: Skew Protection for your Kubernetes apps, built right into the Platformatic Intelligent Command Center (ICC). Think Vercel-style deployment safety, but running in your own K8s cluster. No migration needed. Here's why it matters. 🧵

Every engineering team hitting scale with AI faces the same headache: what started as a simple provider integration becomes an operational nightmare. Usage tracking, cost containment, and audit trails slip out of reach fast. 🧵 Here's how we solved it.

Every Node.js developer has lost a background job to a server restart. We just open-sourced @platformatic/job-queue, a new queue library built for reliability from day one. Deduplication, retries, request/response, graceful shutdown. All out of the box. 🧵👇

Thank you Anthropic for the Open Source support!

Most developers I know complains about the performance of Web Streams. I'm glad that my friend James Snell is trying to fix it. Here is a new proposal for streams in JS. In some cases, this is a 90x throughput increase. You've read it right! blog.cloudflare.com/a-better-web...

On the next Node (& More) Banter: @lucamaraschi and I break down how to build AI apps that are fast AND auditable From black box to transparent—designing for explainability from day one.

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...

🚀 I'm running a 4-hour intensive workshop at CityJSConf London! High-Performance Node.js: From Event Loop Mastery to Production Observability 📅 April 16, 2026 9:00 AM 📍 CityJS London, Day 2 This is everything I've learned building Fastify, Pino, and Undici — packed into one session.

🎉 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-...

There is a category of security researchers who are a threat to the Open Source ecosystem. 🧵

My hot take on LLM copyright issues is that it's just exposing how ridiculous software licenses are. The pirates were right all along, you can't give something away and tell people how they may use it.

🔥 NEW BANTER: "Double the Density. Half the Memory." with James Snell What if your Node.js apps used 50% less memory tomorrow? Not by rewriting anything. Not by changing a single line of code. Luca and I sit down with James to explain how 📅 Feb 25th 🔗 streamyard.com/watch/W7nF2j...

Landed initial support for ESM in Node.js SEA: github.com/nodejs/node/... Similar to CJS entrypoints, it only supports importing builtins, so generally require bundling. @nodeland.dev is working on support for VFS in SEA that will unlock loading other modules within SEA github.com/nodejs/node/...

Here is what I taught Opus 4.6 today: > When using once(), the listener must be registered before the operation that might trigger the event. Otherwise, fast jobs might complete before the listener is attached, causing tests to hang indefinitely waiting for events that already occurred.