Install
pnpm create vinext-app@latest my-appWho it is for
This skill fits people already writing Next.js who want to move to Vite and treat Cloudflare Workers as the main deploy target. Officially it is written as: run a Next.js app on Vite, with Cloudflare Workers as the first landing environment. It also fits people ready to create a sample directory on this machine and accept that the official create command writes to disk.
The source also says it can work with Claude Code, OpenCode, Cursor, Codex, and many other AI coding tools. That is a sample list, not support for only those four. If you only ship a static page, or the deploy target is not Workers at all, stay with reading the notes.
It also does not fit treating a live production app as something that “just runs after a swap.” Officially: today it can carry quite a few substantial Next.js apps, but it is not yet a plug-and-play replacement for every app or production load. The official repository is https://github.com/cloudflare/vinext Operate with commands already written on that page.
First attempt in 3 minutes
Follow only the new-project path the official page writes.
Prerequisite: this machine can run pnpm, the current directory may create a new folder, and you clearly agree to one local init. First confirm: the command below will create a new directory named my-app. If you do not yet want to write to disk, do not run it.
Install location: open a terminal in the directory where you want the new project, confirm the side effects above, then run:
pnpm create vinext-app@latest my-app
Low-risk check: after the directory appears, only read the project notes and config. Do not deploy, and do not change a live repository. If you opened an existing Next.js project, the next sentence the source gives is to say migrate this project to vinext in a supported tool; on the first attempt, stop at restating what that sentence would change — do not let the tool change files yet.
Success signal: my-app appears in the current directory, and you can see it is a Next.js-on-Vite project built by vinext. If the command fails, do not invent an installer that never appeared; go back to the official page and check the source text.
Usage cases
Case 1: From scratch, build a Vite-based Next.js project aimed at Cloudflare Workers. The official command is pnpm create vinext-app@latest my-app. It fits people who want an inspectable local directory first, then decide whether to keep developing. Before acting, confirm there is no folder of the same name. If the source does not say how to skip install or change the deploy target, do not assume such a switch exists.
Case 2: Judge whether an existing Next.js project should move to vinext. The source says: open that project in any supported tool and say migrate this project to vinext. The first time, have the tool list which files it would change, then allow writes only after you confirm. The source does not give a list of covered routes, data fetching, or middleware, so you can only “start the evaluation with the official phrase”; do not invent a compatibility table that was never written.
Boundaries
The official main path is pnpm create vinext-app@latest my-app. Do not write an unappeared installer into the main path. On deploy, the source only writes Cloudflare Workers as the first target; it does not prove you can push unchanged to an unnamed platform.
The capability boundary is clear: today it can carry quite a few substantial Next.js apps, but it is not yet a plug-and-play replacement for every app or production load. Do not use it to promise a zero-change cutover of a live site.
The tool list is Claude Code, OpenCode, Cursor, Codex, and many other AI coding tools — a sample, not a closed list. Only one migration phrase is written in the source. Secrets, environment variables, and production-release steps are not expanded; do not fill them in. The official page is https://github.com/cloudflare/vinext If a tool suggests a command that disagrees with that page, treat that page as authoritative.