cloudflare / vinext

migrate-to-vinext walks an AI agent through moving an existing Next.js project onto vinext — Cloudflare's from-scratch reimplementation of the Next.js API surface on top of Vite, built primarily for deploying to Cloudflare Workers. Its own description covers compatibility scanning, replacing the next package with vinext, generating the Vite config, converting to ESM, and wiring up deployment; in practice it's an agent-driven front end for the same logic vinext's own vinext init and vinext check commands already run non-interactively.

This is for someone migrating an existing Next.js application onto Cloudflare Workers who wants an agent to drive the process and explain compatibility gaps as it finds them, rather than running vinext init and reading the output themselves. It has nothing to offer someone starting a fresh project (pnpm create vinext-app covers that) or running vinext outside an agentic coding tool.

READ THE FULL ANALYSIS＋

vinext itself is young. Cloudflare's own readme calls it under active development and says it is not yet a drop-in replacement for every Next.js application. It names specific gaps directly: partial "use cache" and Cache Components support, incomplete build-time image and font optimization, and native modules such as sharp and lightningcss that can fail inside the Vite dev server. The skill inherits whatever vinext itself can't yet do; it doesn't paper over the gaps.

What it costs to use it. The skill is labelled local_tool in our data: it assumes you can already run npx inside a Next.js project and shells out to vinext's own CLI rather than working through an API or an account. There is no separate credential or subscription requirement beyond having Node and the project itself.