Запускайте Next.js приложений на Vite, при этом Cloudflare Workers являются основной целью развертывания.

Веб-сайт: vinext.dev

Документация: vinext.dev/docs

Читайте объявление: Как мы восстановили Next.js с помощью ИИ за одну неделю

Активная разработка. vinext поддерживает значительное количество Next.js приложений сегодня, но пока не является прямой заменой для каждого приложения или производственной нагрузки. Ожидайте пробелов в совместимости, особенно в новых функциях App Router, и оценивайте их по сравнению с вашим приложением перед внедрением.

vinext ререализует поверхность API Next.js на Vite, а не потребляет вывод next build. Он поддерживает как App Router, так и Pages Router, компоненты React Server, Server Actions, промежуточное ПО, обработчики маршрутов, ISR, статический экспорт и наиболее часто используемые модули [[T1]. 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.