---
title: "Cloudflare Migrate to vinext: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/cloudflare-migrate-to-vinext/
description: "Migrates Next.js applications to Cloudflare Workers via vinext (Vite-based Next.js reimplementation), handling ESM conversions and worker deployment."
---

# Cloudflare Migrate to vinext: review, setup & limitations · Undominated.ai

> Migrates Next.js applications to Cloudflare Workers via vinext (Vite-based Next.js reimplementation), handling ESM conversions and worker deployment.

[← Explore all skills](/skills/)

WEB FRAMEWORKS / Cloudflare

# Cloudflare Migrate to vinext

Migrates Next.js applications to Cloudflare Workers via vinext (Vite-based Next.js reimplementation), handling ESM conversions and worker deployment.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/cloudflare/vinext)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 3 linked sources
 Publisher Cloudflare
 Licence [MIT ↗](https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/LICENSE)
 Revision 82458b4252f6
 [Read what was—and wasn’t—checked ↓](#review)

“Migrates Next.js projects to vinext (Vite-based Next.js reimplementation). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles compatibility scanning, package replacement, Vite config generation, ESM conversion, and deployment setup …”

 [Cloudflare · upstream description ↗](https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Migration is defined as a package and config change, not an application rewrite.
- The skill stops immediately when package.json has no next dependency.

### A good fit for

 - Moving an existing Next.js app onto vinext and Vite
- Deploying that app to Cloudflare Workers with cloudflare:workers bindings
- Assess a Next.js-to-vinext migration before replacing the deployment path.

### Weigh up before choosing

 - The file says not to rewrite next/* imports and not to copy webpack or Turbopack config into Vite.
- next/image optimization and next/font/google self-hosting are listed as known limitations.
- Cloudflare bindings must not be reached through getPlatformProxy, getRequestContext, or a custom worker fetch(request, env).
- This review did not execute the skill.
- The opening no-application-changes claim is not a compatibility guarantee. ESM conversion, ecosystem plugins, middleware and runtime differences need actual tests.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - .agents/skills/migrate-to-vinext/SKILL.md
- .agents/skills/migrate-to-vinext/references/compatibility.md
- LICENSE

### Our findings

 - The pinned skill starts by confirming next is a dependency and by detecting the package manager from the lockfile, and it stops if next is absent.
- The recommended path is vinext check, then vinext init, which installs Vite, sets type module, and can add the React Server Components plugin for the App Router.
- Manual fallback renames CJS configs to .cjs, replaces next dev with vite dev, and points config variants at references/config-examples.md.
- Workers deployment prefers npx @vinext/cloudflare deploy, and bindings are imported from cloudflare:workers rather than older proxy helpers.
- The automated path retains Next.js alongside new scripts, while the manual fallback performs explicit package and configuration changes.

### Not established by this review

 - The skill was not executed inside a host agent.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md)

DOCUMENTED COMMAND

 npx skills add cloudflare/vinext/.agents/skills/migrate-to-vinext Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/cloudflare/vinext/tree/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext Copy reviewed-revision command ↗ - Install the skill into your coding agent workspace.
- Verify Next.js presence in package.json before running migration steps.

### Before you start

 - Node.js runtime with pnpm, yarn, npm, or bun
- A Next.js application codebase

### Compatibility

Agent Skills hosts · Next.js 13/14/15 · Cloudflare Workers / workerd runtime

### Implementation

Markdown · TypeScript

### Next.js to Cloudflare Workers migration workflow

 - Edit package.json, vite.config.ts, and gitignore
- Run vinext check, vinext init, and the dev server
- Deploy with the Cloudflare or Nitro command only when the user wants deployment
- Changes package/config/module formats and may deploy Workers or another target with separate credentials.

### Cost model

MIT licence; Cloudflare Workers deployment needs a Cloudflare account, which the file treats as optional.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Cloudflare vinext migration skill definition ↗](https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext/SKILL.md) Checked 2026-10-14 https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext/SKILL.md Supports: summary, whySelected, bestFor, limitations
- [Cloudflare vinext license ↗](https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/LICENSE) Checked 2026-10-14 https://github.com/cloudflare/vinext/blob/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/LICENSE Supports: license
- [2026-10-15 W41 source re-review at the existing pin ↗](https://raw.githubusercontent.com/cloudflare/vinext/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/cloudflare/vinext/82458b4252f66ebd6fae0f7b0ad026a8e7c5718b/.agents/skills/migrate-to-vinext/SKILL.md Supports: upstreamDescription, review.notTested, review.reviewedAt

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Cloudflare cf CLI ↗ Pins Cloudflare's cf CLI skill, which tells an agent to search the local command index and to keep Wrangler when a Wrangler config is already present.](/skills/cloudflare-cf-cli/)[### Cloudflare product discovery ↗ Pins Cloudflare's product-discovery skill, which blocks a new Wrangler setup, runs cf migrate only when asked, and says a version rollback does not restore resource data.](/skills/cloudflare-cloudflare/)[### Cloudflare Sandbox preview migration ↗ Pins Cloudflare's stable-to-preview Sandbox migration, which refuses an unagreed production cutover and forbids invented APIs and live secrets in the sandbox environment.](/skills/cloudflare-sandbox-migrate-to-next/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
