AI Summary
5 min readSteve Faulkner, Cloudflare's Director of Engineering for Workers, shares how he used AI to create V Next—a port of Next.js to Vite—in a weekend, dubbed a "slop fork" for its AI-generated code. The project demonstrates AI's potential to accelerate large-scale engineering tasks when guided by human direction, focusing on replicating Next.js behavior via its test suite rather than pristine code.
Motivation and Setup
Cloudflare sought better Next.js support on Workers, as Next.js ties closely to Node and Vercel runtimes, causing issues elsewhere. Manual proofs-of-concept estimated 5 engineers and 6 months; an intern's attempt also failed. With recent AI advances (Claude Opus 4.5/4.6), Faulkner tested porting Next.js by targeting its 8,000+ tests, starting with a Friday evening plan to cover app router, pages router, and key features like code generation.
Planning Process
Planning took a few iterative hours using voice-to-text (SuperWhisper) and Markdown files in OpenCode: a main plan.md, testing.md, and later discoveries.md for bugs (e.g., React DOM CJS issues). He guided AI to port relevant tests to Vite Test and Playwright, avoiding full Next.js suite complexity. Background knowledge of Next.js and Vite shaped the scope; AI handled porting tests and implementing fixes, with human vetoes on out-of-scope ideas like ripping out React.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of Syntax - Tasty Web Development Treats
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 **[00:00] Intro to V Next and "Slop Fork" Drama**
- 2 **[03:21] Why Fork Next.js on Cloudflare**
- 3 **[06:28] Initial Planning Process**
- 4 **[09:41] AI Workflow: Sessions, Models, and Automation**
- 5 **[14:32] Debugging, Tools, and Context Management**
- 6 **[18:53] Feedback Loops and AI Behaviors**
- 7 **[21:24] Code Quality, Guardrails, and Security**
+ Full timestamped outline available in the app
Show Notes
Wes and Scott talk with Steve Faulkner about vinext, a Vite-powered Next.js fork. They dive into AI coding workflows, agent browsers, code quality, and what modern dev tooling looks like in an AI-first world.
Show Notes
- 00:00 Welcome to Syntax!
- 02:01 Knowing how to use AI
- 02:31 The idea behind “slop fork”
- 06:27 How to approach a project like this
- 07:53 Using markdown as a planning and thinking tool
- 12:35 Steve’s OpenCode setup
- 14:31 What agent browsers are and how they work
- 15:34 Where agent browsers fall short
- 19:02 Why agents work best with tight feedback loops
- 21:23 Dealing with poor code quality from AI
- 23:54 Brought to you by Sentry.io
- 24:19 Searching for a reliable AI workflow
- 25:54 What about security?
- 28:46 When it makes sense to port a framework vs switch
- 32:03 What an AI-first programming language might look like
- 33:16 TypeScript in an AI-driven workflow
- 35:36 Cloudflare and improving developer experience
- 38:10 Being excited and uneasy about where AI is heading
- 39:06 Which industries AI disrupts next
- 41:2
More from this podcast
Syntax - Tasty Web Development Treats →