# Cloudflare just slop forked Next.js… Source: https://www.youtube.com/watch?v=abbeIUOCzmw Recap page: https://rapidrecap.app/video/abbeIUOCzmw Generated: 2026-03-02T21:01:42.555+00:00 --- ## Quick Overview Cloudflare rebuilt the Next.js API surface on Vite, creating vinenext, which achieved significant performance gains (up to 4.4x faster build times and 57% smaller client bundles) compared to Next.js 16 with Turbopack, though the migration process required using an AI agent (OpenNEXT) to handle complex refactoring, especially converting CommonJS to ESM and fixing JSX syntax issues. **Key Points:** - Cloudflare rebuilt the Next.js API surface using Vite and Rollup/Rousedown, resulting in a new project called vinenext. - Vinenext demonstrated significant performance improvements, achieving build times up to 4.4x faster than Next.js 16 with Turbopack (1.67s vs 7.38s). - Client bundle sizes for vinenext were up to 57% smaller compared to Next.js 16 (72.9 KB vs 168.9 KB). - The migration process from Next.js to vinenext was facilitated by an AI agent skill called OpenNEXT, which performs automated refactoring. - Cloudflare previously attempted a similar project but failed due to the enormous scope involving routers, module shims, and complex pipelines. - The key difference enabling the success this time was the use of AI coding agents, which helped resolve issues like converting JSX files to .jsx and handling module resolution differences between Vite and Next.js. - Despite success, the speaker suggests that for most users, migrating from Next.js to vinenext is 'Not Yet' worth the effort due to the bleeding edge nature of the technology. ![Screenshot at 0:04: The initial comparison slide showing the logos for Ruby on Rails and Django, and MySQL versus MongoDB, setting the stage for a discussion on major technology rivalries, which quickly pivots to the Vercel/Cloudflare dynamic involving Next.js and vinenext.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-00-04.jpg) **Context:** This video discusses the recent development by Cloudflare, where they rebuilt the core features of the Next.js framework using Vite as the underlying bundler, naming the resulting project 'vinenext'. This effort is framed against previous, unsuccessful attempts by Cloudflare and others to create a more performant alternative to Next.js. The video contrasts the performance metrics of vinenext (using Vite 8/Rolldown) against the official Next.js 16 using Turbopack, highlighting substantial gains in build speed and bundle size. ## Detailed Analysis The video details Cloudflare's project to rebuild the Next.js API surface on top of Vite, resulting in 'vinenext'. This was motivated by the complexity and performance limitations of Next.js's existing build tooling. Cloudflare previously attempted this feat but failed due to the massive scope, which included complex server rendering pipelines, RSC streaming, and extensive module shims. The successful attempt utilized AI, specifically an agent skill called OpenNEXT, which automated much of the required refactoring. The performance benchmarks are striking: vinenext (Vite 8/Rolldown) achieved production build times 4.4x faster than Next.js 16 (Turbopack) (1.67s vs 7.38s) and resulted in client bundle sizes 57% smaller. The AI agent successfully converted configuration files (like postcss.config.js) and refactored JSX files to use the .jsx extension required by Vite. However, despite the technical success demonstrated by the benchmarks and the successful migration of the 'Bytes' newsletter application, the presenter concludes that it is 'Not Yet' worth it for most developers to switch due to the bleeding-edge nature and potential instability, symbolized by a finger bleeding after an accidental poke. ### Tech Rivalries Context - Rails vs Django - SQL vs NoSQL - Web Components vs Feelings - Cloudflare vs Vercel (Divergence announcement) ### The vinenext Project - Next.js API surface reimplemented on Vite, built on the OpenNEXT open-source adapter project - Goal: Free Next.js apps from Vercel's deployment constraints ### Performance Benchmarks (Source - Cloudflare TMB bench): Vinenext (Vite 8/Rolldown) is 4.4x faster in build time (1.67s) and 57% smaller in client bundle size compared to Next.js 16/Turbopack. ### Migration Process via AI Agent - Used 'npx skills add cloudflare/vinenext' skill - AI successfully handled JSX to .jsx conversion and added 'type: "module"' to package.json. ### Post-Migration Issues - Initial deployment failed because React Server Components (RSC) were not supported, requiring manual fixes like changing 'createRequire' calls to use ESM imports in configuration files. ### Conclusion & Verdict - The project worked, achieving significant speedups, but the speaker advises against adoption for general users yet, as bleeding edge development means potential issues still exist. ![Screenshot at 0:01: Two men in an intense, exaggerated argument in a park, setting a tone of rivalry.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-00-01.jpg) ![Screenshot at 0:04: Visual comparison of framework logos: Rails vs Django and MySQL vs MongoDB, establishing the theme of tech conflicts.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-00-04.jpg) ![Screenshot at 0:15: The core rivalry introduced: Vercel vs Cloudflare, preceding the discussion about Next.js and vinenext.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-00-15.jpg) ![Screenshot at 0:40: A graphic showing the 'stairway to heaven' leading to the GitHub logo, symbolizing the open-source aspiration for the new framework.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-00-40.jpg) ![Screenshot at 2:22: Benchmark comparison showing Rolldown \(Rust-based bundler used in vinenext\) is significantly faster than Rollup + Esbuild for bundling 19k modules.](https://ss.rapidrecap.app/screens/abbeIUOCzmw/00-02-22.jpg)