Vite上でNext.jsアプリケーションを実行し、Cloudflare Workersを主な展開ターゲットとします。

ウェブサイト: vinext.dev

ドキュメント: vinext.dev/docs

発表を読んでみてください: 1週間でAIでNext.jsを再構築した方法

現在開発中vinextは現在、多くのNext.jsアプリケーションをサポートしていますが、すべてのアプリケーションや本番ワークロードの即用代替ではありません。特に新しいApp Router機能では互換性のギャップが予想され、採用前に自社のアプリケーションと比較して評価してください。

Vinextはnext buildの出力を消費するのではなく、Vite上でNext.js APIサーフェスを再実装します。App RouterおよびPagesルーター、Reactサーバーコンポーネント、サーバーアクション、ミドルウェア、ルートハンドラ、ISR、静的エクスポート、そして最も一般的に使われる[next/*モジュールの両方をサポートしています。Cloudflare Workersは最も深い統合能力を持っています。Node.jsやその他のプラットフォームは、さまざまなサポートレベルで利用可能です。

プロジェクトの現状

今日うまくいくもの

• **App RouterおよびPages Router 開発および本番ビルドにおける
• 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.