chris-bzst

The most interesting thing here isn't the framework itself — it's theapproach. They didn't wrap Next.js output or try to patch it for Workers. They treated the Next.js API surface as a spec and reimplemented it on top of Vite from scratch.

The Traffic-aware Pre-rendering idea is genuinely clever. Instead of pre-rendering every possible route at build time (and waiting 30 min for large sites), they query actual Cloudflare zone analytics at deploy time and only pre-render the pages that get real traffic. Power law does the rest — a few hundred pages cover 90%+ of hits, everything else falls back to SSR + ISR.

The "$1100 in API costs" headline is catchy but I think the real takeaway is more subtle: this worked because all four preconditions happened to line up — Next.js is extremely well-documented in training data, it has a massive test suite you can port as a mechanical spec, Vite handles the genuinely hard bundler problems, and current models can sustain coherence across a codebase this size. It's not "AI can replace any framework in a week" — it's "given the right constraints, one person can move way faster than we assumed."

Curious to see how well it holds up as Next.js keeps shipping new APIs. The 94% coverage number is impressive today but compatibility is a treadmill.

This is seriously awesome! Lovable and v0 better start worrying!