Cloudflare just slop forked Next.js…

Throughout history, there have been some rivalries that have shaped our lives as developers. Rails versus Django, SQL versus NoSQL, web components versus feeling the love and embrace of a woman. And just a few days ago, we got another update in one of my favorite niche tech rivalries, Versel versus Cloudflare. If billionaires passive aggressively having a downtime measuring contest on your timeline isn't your thing, you may have missed that Germo from Verscell and Matthew from Cloudflare really don't like each other. And that rivalry got amped up even more last week when Cloudflare released V-Next, a re-implementation of the Nex.js API built on V, essentially freeing up your Next.js app to be deployed anywhere. In this video, we'll break down how they did it, what it may mean for other open- source projects in the future, and find out if it actually works. It is March 2nd, 2026, and you're watching the code report. Love it or hate it, Next is still the most popular way to create a React app. But despite that, historically its biggest weakness has had nothing to do with its API, but rather its lack of deployment targets. If you have a next app and you want to deploy it on Versell, cool. Everything will work nice since Verscell essentially provides a bespoke runtime for things like routing, middleware, ISR, and image optimization. But if you have a next app and you want to deploy it somewhere not on Verscell, like Cloudflare, or Netlefi, it gets a little trickier. If you've had this constraint, odds are you've used the Open Next project to get around it. The way Openext works is it takes the traditional output you get from running next build and then repackages it to run on whichever platform you'd like. And as you might imagine, this process of needing to reverse engineer and build on top of next output is fragile and prone to errors as the build output changes over time. So the crazy folks at Cloudflare got together and thought, what if instead of building on top of the output, we just entirely rebuilt the next framework from scratch on Vit. Now this isn't a novel idea and it's not the first time it's been tried. Cloudflare themselves had even tried it in the past and failed. So what makes this time different? Well, obviously AI. It took them just one day to get basic SSR, middleware, server actions, and streaming to work. But by day three, they were able to deploy to Cloudflare workers with full client hydration. And then they spent the rest of the week fixing edge cases, expanding the test suite, and bringing API coverage up to 94% of the next API. All for about a grand total of $1,100 in AI tokens. And because it's built on Vit, it can take advantage of Vit's architecture, which includes rolldown, the Rustbased bundler for improved performance. So what does Verscell think about all this? As you can imagine, they're not the biggest fans. The Verscell CTO tweeted about it being a quote slop fork, and Gromo himself tweeted a Cloudflare to Verscell migration guide and some critical vulnerabilities that they found in the project. Those vulnerabilities make it feel like a true Nex.js clone, but since I know you don't have any actual users, that doesn't matter. So, let's find out if it actually works. Here's the app for our newsletter, byes.dev. It's a pretty generic next app that allows people to sign up for the newsletter and displays an archive of our past issues, which it gets from disk. We also have an endpoint that spits back HTML that we can paste into our email platform for sending. For basic apps, you could probably just install V-Next and swap out the next command for it in your package JSON and it may work. But for this one though, we'll need some refactoring to get it working with V. Thankfully, Cloudflare also built an agent skill to make it pretty simple. Since I'm using cursor, I can install it with this command and then once it's installed, the agent can use it when it helps migrate the project to V-Next. The biggest thing to look out for is compatibility with V. For example, it'll add type module in our package JSON so that all the JS files in the project will be treated as ES modules. And it'll refactor any JS files that have JSX in them to use the JSX extension since it's required by V. And my favorite part is when it says it's done, even though half the app is still broken. But after some follow-up begging, it did eventually figure it out. And we now have our next app running entirely on V. The big question is, was it worth it to switch to be honest, probably not yet. Always remember, when it comes to bleeding edge software, you're the one who bleeds. Beyond the slop narrative, though, I think the more interesting part is how great V is. In Cloudflare's own Trust Me Bro benchmarks, they found that production build times with V-Ex were up to 4.4 four times faster than next and the client bundle size was 57% smaller both almost entirely because of vit and rolldown and in my own I probably screwed something up so don't trust me pro benchmarks I was able to achieve 5x faster builds on the bites website with v- next build times are never something I really care to optimize so I'm not going to ship it to production but it's interesting enough that I'll check back on the project in a few months and no matter how much code agents write for you still need to understand how that code works under the hood and the best way to do that is by mastering computer science science fundamentals with Brilliant, the sponsor of today's video. I'd highly recommend their algorithmic thinking course where you'll learn how to design algorithms from first principles to solve classic computer science problems. The best part was learning how to implement greedy optimizations which are built to make the locally optimal choice at each step in order to reach the overall global optimum. And you'll learn all these techniques by solving actual problems created by MIT professors, not just watching videos. Then scan the QR code or use the link in the description for a free 30-day trial and 20% off their premium subscription. This has been the Code Report. Thanks for watching and I will see you in the next one.