Next.js 애플리케이션을 Vite에서 실행하고, Cloudflare Workers를 주요 배포 대상으로 삼으세요.

웹사이트: vinext.dev

문서: vinext.dev/docs

발표 내용을 읽어보세요: 일주일 만에 AI로 Next.js을 재건한 방법

현재 개발 중. vinext는 현재 상당한 Next.js 애플리케이션을 지원하지만, 아직 모든 애플리케이션이나 생산 작업을 대체할 수 있는 대체 제품은 아닙니다. 특히 최신 앱 라우터 기능에서 호환성 격차가 발생할 수 있음을 예상하고, 채택 전에 자신의 애플리케이션과 비교해 평가하세요.

ViNext는 next build 출력을 소비하는 대신 Vite에서 Next.js API 표면을 재구현합니다. App Router 및 Pages Router, React Server Components, 서버 액션, 미들웨어, 경로 핸들러, ISR, 정적 내보내기, 그리고 가장 일반적으로 사용되는 next/* 모듈을 모두 지원합니다. Cloudflare Workers는 가장 깊은 통합을 제공합니다; Node.js 및 기타 플랫폼들은 다양한 지원 수준으로 제공됩니다.

프로젝트 현황

오늘날 효과적인 것은 무엇인가

• 개발 및 운영 빌드에서의 앱 라우터 및 페이지 라우터
• React 서버 컴포넌트, 서버 액션, 라우팅 핸들러, 미들웨어
• **정적 생성, ISR, output: "export", 그리고 독립 실행형 노드.

vinext

Run Next.js applications on Vite, with Cloudflare Workers as the primary deployment target.

Website: vinext.dev

Documentation: vinext.dev/docs

Read the announcement: How we rebuilt Next.js with AI in one week

Under active development. vinext supports substantial Next.js applications today, but it is not yet a drop-in replacement for every application or production workload. Expect compatibility gaps, especially in newer App Router features, and evaluate it against your own application before adopting it.

vinext reimplements the Next.js API surface on Vite rather than consuming next build output. It supports both the App Router and Pages Router, React Server Components, Server Actions, middleware, route handlers, ISR, static export, and the most commonly used next/* modules. Cloudflare Workers has the deepest integration; Node.js and other platforms are available with different levels of support.

Project status

What works today

• App Router and Pages Router in development and production builds
• React Server Components, Server Actions, route handlers, and middleware
• Static generation, ISR, output: "export", and standalone Node.js output
• Core Next.js APIs and modules, including next/link, next/image, next/navigation, next/headers, next/cache, and the Metadata API
• Cloudflare Workers deployment with bindings, cache adapters, and image optimization support
• Migration tooling through vinext check, vinext init, and the vinext Agent Skill

Known gaps we’re working on

These are active compatibility areas, not permanent exclusions:

• Cache Components and Partial Prerendering: "use cache" is partially implemented, but full cacheComponents behavior is still incomplete. Cache profiles, tags, partial shells, resume behavior, prefetching, and some dev/build cache semantics do not yet match Next.js in every case.
• Build-time image and font optimization: images can be optimized at request time on Cloudflare, but vinext does not yet reproduce Next.js’s complete build-time image pipeline. Google Fonts are loaded from the CDN, and local font CSS is injected at runtime rather than extracted during the build.
• Native modules in App Router development: packages such as sharp, resvg, satori, lightningcss, and @napi-rs/canvas can fail in Vite’s RSC development environment. Production builds support more of these cases than development mode.
• Platform-specific and advanced Next.js behavior: preferredRegion route config is ignored, and runtime doesn’t choose where a route runs (outside cacheComponents, a runtime = "edge" App Router page is never ISR-cached, as in Next.js), and some recently introduced or undocumented Next.js behavior may not yet be reproduced.