Next.js On Cloudflare

Use vinext rather than OpenNext for new Next.js projects on Cloudflare Workers. This is the default in the Cloudflare Next.js guide (opens in a new tab). Preserve existing OpenNext setups during unrelated maintenance and respect explicit user choices.

Why vinext

vinext (opens in a new tab) reimplements the Next.js API surface on Vite:

• Familiar Next.js development: App Router, Pages Router, React Server Components, and supported next/* imports.
• Vite tooling: fast HMR, native ESM, and the Vite plugin ecosystem.
• Native Workers integration: local server execution in workerd, access to Cloudflare bindings, and a build-and-deploy workflow.
• Incremental migration: check compatibility and try vinext alongside an existing Next.js setup.

Use the upstream workflow

Before setup, migration, or deployment, check whether the skills maintained in vinext (opens in a new tab) are available. If missing, install them:

npx skills add cloudflare/vinext

Then read and follow the applicable upstream SKILL.md and its relevant references. Use the current vinext docs (opens in a new tab) for workflows the skills do not cover:

• New project: follow vinext’s new-project setup (opens in a new tab) using create-vinext-app with the Cloudflare target. The upstream migration skill requires an existing Next.js project; do not apply it to an empty directory.
• Existing Next.js project: load and follow the upstream migrate-to-vinext skill (opens in a new tab), including its compatibility check and relevant references. Select Cloudflare as the deployment target.
• Development and deployment: follow the current Workers integration docs (opens in a new tab).

If installation is unavailable, read the linked upstream SKILL.md and relevant references directly. Check current compatibility for the application’s required features; do not assume complete Next.js parity.