Over a week into rewriting the Nitro external resolver/tracer plugin. Only ~100 LOC, but tiny details have a big impact on performance and build stability. In large projects, resolver hooks may be called thousands of times, doing less really matters.

🔖 mirandaheath.website/report-on-bu...

“one” added dep and node_modules turns into a pile of extra crap. Try: npmgraph.js.org WARNING: Once you see it, you can’t unsee it.

Glad to see more projects are being built on top of the h3.dev composable ecosystem ⚡️

Nitro v3’s filesystem routing is now optional by default ✨ Choose what fits your setup best: 📂 Filesystem routing (serverDir: "server") ⚙️ routes: {} config 🧩 server.ts (bring your own router) All core routing features remain available.

Are we getting PHP in JS? And how is this related to @vite.dev and SSR? I've taken a look at Rendu, the hypertext preprocessor also used by the upcoming @nitro.build v3 youtu.be/Qk2oNBRw2Y8

Build → Refine → Clean up → Repeat ↻

🇨🇭 Nitro Modules → Vite Plugins Working on a POC to make Vite plugins interoperable as Nitro modules. This could help create a more unified ecosystem of universal plugins.

POV: We add a bunch of polyfills and fixes in libraries only because developers make mistakes. This costs end users! EVERY RUN, EVERY CALL, EVERY REQUEST... probably billions of times!

Looking for a reliable way to detect AI agents executing CLI scripts with @danielroe.dev, so we can adjust verbosity and capture spans. Ideas welcome! github.com/unjs/std-env...

Migrating Nitro (dist) from Rollup to @rolldown.rs : CI time dropped from 36s → 7 s ++ few issues got fixed 😎

🧹 Time to clean up! unjs/ofetch ($fetch) v2 (alpha) - 🌐 ESM-only + Native Web APIs - 📦 Zero deps (3 → 0) - 📉 Install: 900 KB → 28 KB - ⚡️Bundle: 17.4 KB (6.5 KB gz) → 6.3 KB (2.4 KB gz) More optimizations to come 🤞

💡We can hide internals with ~ instead of _ for btter DX:

Pushing Nitro and H3 to their limits! Full server bundle: 12 KB (~4.5 KB gzip) with 95%+ bare-runtime performance — and still improving. The Nitro + H3 + Vite stack is nearing a truly seamless, runtime-agnostic full-stack server toolchain.

🪝 Hookable powers Nuxt & Nitro hooks — every build, request, and render calls it. 🔥 v6.x (rc): 20–35× faster and 79% smaller (−2.26 KB) (with HookableCore) Thanks @negezor for the perf magic ✨

Time for a first look into the @nitro.build v3 alpha, which is just a @vite.dev plugin 👀 youtu.be/sWGWHyVlIlU

Intresting...

🔥 The most universal format for JavaScript servers is simply { fetch } Already in: ⚙️ Runtimes: Deno | Bun | Node.js (via srvx) 🧩 Frameworks: H3 | Hono | Elysia | Nitro | Remix ☁️ Platforms: Vercel Fluid | Cloudflare Workers | Deno Deploy | Netlify Edge

I’ll be writing a full article soon about what’s happened with @nitrojsdev v3 so far — and what’s ahead. 🤞

@nitro.build just hit GitHub Trending — let’s nitrooo! 🚀🔥

Who buys iphone air when you can get this for €20 from temu! 16GB Rom, 2GB Ram, Dual sim, super slim and light!, camera, flashlight, multi touch good speakers, even comes with a bumper and screen protector!

👀 Put together a repo using @angular.dev SSR w/AngularAppEngine + @vite.dev + @nitro.build v3 github.com/brandonrober...

Heck yeah! The @nitro.build v3 beta is out now. And Nitro is now just a @vite.dev plugin 👀 Kudos to all contributors, @unjs.io, and @pi0.io 🙌🏻

Finally, we got PHP in JavaScript! 👀

Reverse JSX? Instead of HTMLish syntax in JS, JSish syntax in HTML 🤭

What if I told you your Vite SPA could do partial server-side rendering and streaming? 😌 Let’s talk about how. 👇 (1/1)

Coolest part: LLMs understood the syntax instantly! No explanation needed; most completions were single-shot correct. Turns out, using familiar patterns (PHP-like + Web API) really pays off.

Introducing Rendu: JavaScript Hypertext Preprocessor Not just a template engine — Rendu bridges SPA and SSR using modern Web APIs with multi-streaming and async support.

🐘Why not?

JS pro tip: Add { cause } to errors. Makes debugging and inspection way easier 🔍 developer.mozilla.org/en-US/docs/W...

So obsessed with keeping H3Core’s bundle small. It’ll grow over time with more features, so now’s the best chance to make the baseline tiny (currently: 7.5 kB /3 kB gzip).

✨ H3.dev now natively supports { fetch } handler format. This means you can plug in any web-compat framework (like @hono.dev or @elysiajs.com with @nitro.build’s filesystem routing out of the box 🤝 Standards + interop FTW! ❤️

🌶️ Hot take on JS runtimes, based on my obs, take it with a grain of salt. 🚀 Perf: bun > node > deno 🛡 Stability: node > deno > bun 📜 Compliance: deno > node > bun 🧩 Features: bun > deno > node

In Nitro v3, you can use a simple server.ts file for global init and bring the HTTP framework you love — h3.dev, @elysiajs.com, @hono.dev, or anything else ❤️ github.com/nitrojs/nitr...

Full circle achieved 😇😁

⚡️ Jiti v2.6: smaller and faster 📦 Bundle: 2.03 MB → 1.67 MB 🚀 Startup: 150 ms → 22 ms (full transform: 180 ms → 115 ms) Release notes: github.com/unjs/jiti/re...

Running untrusted code even in containers could be unsafe when they have network access with ability to send out env and tokens. This looks like a really promising and composable solution!!

Been working with @pi0.io on a great DX for the upcoming v3 of @nitro.build Stay tuned ⚡︎

🚀 Nitro v3 routing is fully compiled now! ✅ Smaller bundles ⚡ Faster performance 🛠️ More flexibility (extendable route rules) No runtime router — just minimal compiled logic. More to come 👀 github.com/nitrojs/nitr...

This is a must-have initiative! Especially once it becomes a GitHub Action.

TIL: iOS time picker isn’t infinite! it’s just a long list of repeated arrays 😳

The line between multi-vendor and vendor-agnostic is blurry and often mixed up. 🔗 Multi-vendor = locked-in, just with more traps ready to pick from. 🪶Vendor-agnostic = real freedom. 💛 Nitro and UnJS push HARD for the latter.

H3 beta update: - HTTPEvent (use utils outside H3) - Auto Chunked Cookies for Large Sessions - Handles Promise-like values - Send SSE Comments - Sync event.context with req. context (srvx)

NPM provenance and the new trusted publish flow are really cool! we’re already using them for automated nightly releases across @unjs.io Still, I don’t dare replace 2FA with an unattended CI flow for high-download packages. Could we combine CI and 2FA in a secure way? 🤔

🚀 More features just landed for the `srvx` CLI: - Support for Node.js and @expressjs.bsky.social apps* - Custom loader support via --import** (for JSX, etc.) - Quality-of-life improvements - Still zero dependencies and ~100 kB install size

Ubuntu server 25.10 is replacing wget with wcurl 👀 github.com/curl/wcurl

⚠️ A security advisory has been published for IPX. ℹ️ Image assets in directories with the same prefix (e.g., /public123/*) may have been accessible. ✅ All 3 IPX major versions have been patched. Both @nuxt.com and @netlify.com have released updates. ⬆️ Please update to stay safe.

Introducing srvx.h3.dev CLI (experimental). The fastest way to start a modern web server in Node.js, Deno, or Bun.

Did you know that Node.js* supports: ✅ ESM and TypeScript ✅ Watch mode ✅ Web Standard APIs ✅ Arg parser ✅ .env files Now put them all together and Bob’s your uncle! (* Also Deno, and Bun)

🌱 Released H3.dev (beta 2 and 3) today: - Middleware `next()` does not need explicit return - Unhandled errors are logged by default - Experimental `defineRoute` - New `app.request` method (stricter `app.fetch` for runtime safety) We are closer to the stable v2 release 💪