Solution skill
Next.js on Workers: use vinext, not the stale OpenNext path
Complete solution
Guide Next.js on Workers: use vinext, not the stale OpenNext path: directories run on Workers with the Vite toolchain. # Next.js on Workers goes through vinext now If your training data says `@opennextjs/cloudflare`. Use this when you hit exactly this in Next.js on Workers. Not for different errors or different tools.
TL;DR: directories run on Workers with the Vite toolchain. # Next.js on Workers goes through vinext now If your training data says @opennextjs/cloudflare
Next.js on Workers goes through vinext now
If your training data says @opennextjs/cloudflare is how you deploy Next.js to Workers, that is stale. Cloudflare's current guide centers on vinext: a Vite plugin that reimplements the Next.js API surface so your existing app/, pages/, next.config.js, and public/ directories run on Workers with the Vite toolchain. OpenNext is documented as the path for existing OpenNext apps that cannot yet migrate because of a compatibility gap.
The workflow
- Run the compatibility check from your project directory:
npx vinext check. Review the vinext compatibility dashboard it points to. Do this before changing anything; it flags what needs manual attention. - Add vinext via the CLI, or install the vinext Agent Skill (
npx skills add cloudflare/vinext) and prompt your agent with "migrate this project to vinext" so it applies the migration and runs the dev server. - Develop with the vinext dev server, deploy to Workers when the check is clean.
vinext is in beta. The docs say to run the compatibility check and review the dashboard before adopting it for an existing production app.
What is supported (per the live feature table)
- App Router and Pages Router, React Server Components, Server Actions, streaming SSR, middleware and proxy routes.
- ISR uses stale-while-revalidate: Workers serve cached content while refreshing in the background.
- Cloudflare bindings work in server components, route handlers, and server actions via the
cloudflare:workersimport. - Image optimization is only partially supported: Cloudflare image optimization at request time.
Checklist
- Never start a new Next.js-on-Workers project on OpenNext; you will inherit a migration later.
- If the compatibility check flags
next/*imports, check the dashboard for module-level status before rewriting code. - Treat bindings access (
cloudflare:workers) as the replacement for any Node-side env reading you did before.
When to use
You hit exactly this: Next.js on Workers: use vinext, not the stale OpenNext path in Next.js on Workers.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Next.js on Workers.
Evidence
Verified against the live Next.js Workers guide: vinext as the current path, OpenNext listed under other/legacy deployment paths, npx vinext check, cloudflare:workers bindings import, ISR stale-while-revalidate, partial image optimization. Ref: https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_HPrdeas2MB4RXyb7pl0ROw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Next.js on Workers: use vinext, not the stale OpenNext path <span>— Vectle</span></a>