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

If you heard: "Don't bother learning to code, AI will do it all." They're wrong. Here's why. adventures.nodeland.dev/archive/yes-...

We cut @nodejs memory in half with a one-line Docker image swap. No code changes. No new APIs. Just smaller heaps. Here's what happened when we tested pointer compression on real workloads 🧵

I’ll be in Malmö on Feb 25 for the first edition of MalmöJS. We’ll talk about running Node.js at scale: real performance, backpressure, event loop limits, and systems that fail and recover safely. 👉 luma.com/q52blone

🔥 NEW BANTER: "Caching in the Enterprise: Why Most Companies Aren't Doing It" Your app is slow. Your infra bill is climbing. Your database is sweating. And you're probably not caching. Luca and I dig into why... and what to do about it. 📅 Feb 18th 🔗 streamyard.com/watch/vAmndK...

👀 @nodeland.dev has an open PR for a Virtual File System for Node.js 🙏 Yes please! github.com/nodejs/node/...

Only 2 months to go until we celebrate JavaScript in style! 🎉 3 days of talks & workshops sharing the latest trends with top speakers @tej.as @nodeland.dev @nikkitaftw.bsky.social @rich-harris.dev @addaleax.bsky.social @danielroe.dev Secure your spot: london.cityjsconf.org

🔥 NEW BANTER: "HTTP, Queues, Actors: Watt Keeps Node.js Running Smoothly" You're processing HTTP requests and consuming Kafka messages in the same Node.js process. It works. Until it doesn't. @lucamaraschi and I explain what breaks and how to fix it. 📅 Feb 11th 🔗 streamyard.com/watch/3RtsuR...

What does AI mean for someone starting a software engineering career today? I wrote a follow-up to my "Human in the Loop" post. 🧵 👇

Another gem from @nodeland.dev > When AI can implement features faster than any junior developer, what becomes valuable is the judgment to know whether the implementation is correct. And judgment requires understanding. adventures.nodeland.dev/archive/the-...

How am I the first person to repost this after 4 hours? Everyone should listen to these guys! I don't think there's a more crucial source of node.js knowledge getting published right now.

🔥 NEW BANTER: "Scaling Node.js with the Right Signals: ELU" CPU utilization is lying to you. Your auto-scaler adds pods while your actual bottleneck gets worse. Luca and I explain why ELU is the metric you should be watching. 📅 Feb 4th

"Security work is emotionally expensive and invisible, and sharing it makes it sustainable." - @ulisesgascon.com Many thanks to @jddalton.bsky.social, @jordan.har.band, and @ulisesgascon.com for their insights on maintaining Lodash and all the hard work put into reviving the project. 💚

You can vibe code your way to a working prototype. You cannot vibe code or one-shot your way to a competitive product that works at scale. The hard part isn't writing code; it's the architectural supervision.

We just shipped TanStack Start support in Watt. Threw 10,000 requests per second at it on EKS to see what would break. Spoiler: the tail latency improvements are real 🧵

GraphQL is coming home. GraphQLConf 2026 will take place at Meta HQ in Menlo Park, where GraphQL was born. CFP is open and we would love to hear your story 👇 graphql.org/conf/2026/

Like everyone else, I had to build something over the end-of-year break. Mine was GitHuman: a tool to review AI-generated code before you commit. It was built entirely by Claude Code. I reviewed every commit from my phone.

GraphQL is dead. GraphQL is overhyped. GraphQL is only for Facebook-scale problems. We've heard it all. And we disagree. @lucamaraschi and I break down why. 🔥 NEW BANTER: "GraphQL in the Enterprise: Debunking the Myths About Its 'Niche' Problem" 📅 Jan 28th 🔗 streamyard.com/watch/8t67AW...

🔥 I've been debugging @nodejs.org performance for over a decade. The hardest part? Making sense of thousands of stack frames in a flamegraph. What if your AI assistant could do that for you? Today, we're releasing a new feature in `@platformatic/flame`. 🧵

Mike Arnaldi wrote that software development is dead. He's right about a lot of things. But he's missing something critical. I wrote a response 👇 🧵 adventures.nodeland.dev/archive/the-...

Do you like a free tool? Send money. Do you use a tool at work? Convince your employer to sponsor it. Stop marketing OSS as free stuff to your employer, and treat it as a cost for the company. You only endanger the OSS project, if you don't give something in return.

On @netlify.com this has minimal impact: a malicious request can't affect other requests on our serverless architecture, but cold starts + function costs could increase. If your Functions use v18, please upgrade. All others will receive automatic rolling patches: www.netlify.com/changelog/20....

🔥 NEW BANTER: "When Recursion Crashes Your App: The Async Hooks DoS Nobody Expected" Your try-catch blocks won't save you. Your uncaughtException handlers won't fire. Your server just... dies. @lucamaraschi and I break down why. 📅 Jan 21st 🔗 streamyard.com/watch/dwZbc7...

Bun is fast, until latency matters for Next.js. We benchmarked the same Next.js app across Node.js, Deno, Bun, and Watt (our multi-threaded Node-based runtime) under identical load on AWS EKS. Throughput looked fine across the board. Latency told a very different story. 🧵

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