feat(c3): scaffold Next.js apps with vinext instead of OpenNext by scottbuscemi · Pull Request #14896 · cloudflare/workers-sdk

scottbuscemi · 2026-07-28T18:41:12Z

Summary

Makes create-cloudflare --framework=next configure vinext, while keeping opennext available with a flag.

Today C3's Next template only downloads the OpenNext remote template (github:opennextjs/opennextjs-cloudflare/create-cloudflare/next). The docs PR at cloudflare/cloudflare-docs#31887 recommends vinext as the default. This PR makes C3 do the same, with OpenNext retained as an opt-in variant.

Behavior

Interactive (--framework=next) prompts:

vinext (recommended) — default
OpenNext adapter — previous path

Non-interactive:

npm create cloudflare@latest my-app -- --framework=next --variant=vinext
npm create cloudflare@latest my-app -- --framework=next --variant=opennext

-y / --accept-defaults selects vinext.

Changes

templates/next/c3.ts (and experimental re-export):
- Prompt / --variant for vinext | opennext
- vinext → create-vinext-app via runFrameworkGenerator with --platform cloudflare --data-cache none --yes --skip-install --disable-git + matching package-manager flag
- opennext → existing OpenNext remote template (unchanged)
- vinext gets a generated preview script (build && start) so C3's shared previewScript: "preview" works for both variants
Pin create-vinext-app@1.0.0-beta.1 in src/frameworks/package.json (keep create-next-app pin as well)
E2E: next (vinext) + next:opennext in both stable and experimental matrices; getFrameworkConfig tolerates non-platform labels like next:opennext
Changeset included

Generated project shapes

vinext (default)

{
  "scripts": {
    "dev": "vinext dev",
    "build": "vinext build",
    "start": "wrangler dev --config dist/server/wrangler.json",
    "preview": "<pm> run build && <pm> run start",
    "deploy": "vinext-cloudflare deploy --config dist/server/wrangler.json"
  }
}

opennext — same as today's template (opennextjs-cloudflare build/deploy/preview, etc.)

Notes / follow-ups for reviewers

OpenNext remains available via --variant=opennext and the manual OpenNext adapter docs.
--data-cache none on the vinext path avoids a placeholder KV namespace id that would block deploy until the user provisions one.
Companion docs PR: [Workers] Recommend vinext for Next.js cloudflare-docs#31887

Tests
- Tests included/updated
- Automated tests not possible - manual testing has been completed as follows:
- Additional testing not necessary because:
Public documentation
- Cloudflare docs PR(s): [Workers] Recommend vinext for Next.js cloudflare-docs#31887
- Documentation not necessary because:

Note

This is a contribution from an AI agent: opencode, xai/grok-4.5. Opened as a draft for human review before any merge consideration.

Point create-cloudflare --framework=next at create-vinext-app so the generated project matches the recommended Next.js-on-Workers path (vinext dev/build + vinext-cloudflare deploy) instead of the OpenNext remote template.

changeset-bot · 2026-07-28T18:41:25Z

🦋 Changeset detected

Latest commit: 3d4c22e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-cloudflare	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Prompt for vinext (default) vs OpenNext when scaffolding Next.js. --variant=vinext|opennext and -y/--accept-defaults (vinext) cover the non-interactive paths so OpenNext stays one flag away.

scottbuscemi · 2026-07-28T18:50:58Z

Update: OpenNext kept as an opt-in variant

Per review feedback, C3 no longer drops OpenNext entirely. --framework=next now prompts:

vinext (recommended) — default; also selected by -y / --accept-defaults
OpenNext adapter — previous remote-template path

Non-interactive:

npm create cloudflare@latest my-app -- --framework=next --variant=vinext
npm create cloudflare@latest my-app -- --framework=next --variant=opennext

E2E covers both (next and next:opennext). Docs can now truthfully say OpenNext remains available via --variant=opennext (in addition to the manual adapter guide).

workers-devprod · 2026-07-28T20:24:09Z

Codeowners approval required for this PR:

@cloudflare/wrangler

Show detailed file reviewers

.changeset/c3-next-vinext.md: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/helpers/framework-helpers.ts: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/tests/frameworks/frameworks.test.ts: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/tests/frameworks/test-config.ts: [@cloudflare/wrangler]
packages/create-cloudflare/src/frameworks/package.json: [@cloudflare/wrangler]
packages/create-cloudflare/templates/next/c3.ts: [@cloudflare/wrangler]
packages/create-cloudflare/templates/next/experimental_c3.ts: [@cloudflare/wrangler]

ajhawkings · 2026-07-31T16:37:00Z

Curious if this should also be changed in autoconfig (people deploying existing Next apps)?

I've been working on small improvements to Next autoconfig here #14892, but if vinext is the default path, could autconfig run vinext init rather than opennext migrate? I wonder if that works automatically most of the time (and can handle multiple Next versions), or if agents + skill are often needed to migrate?

cc @james-elicx keen to hear what you think 🙂

james-elicx · 2026-08-01T00:33:06Z

Curious if this should also be changed in autoconfig (people deploying existing Next apps)?

I've been working on small improvements to Next autoconfig here #14892, but if vinext is the default path, could autconfig run vinext init rather than opennext migrate? I wonder if that works automatically most of the time (and can handle multiple Next versions), or if agents + skill are often needed to migrate?

cc @james-elicx keen to hear what you think 🙂

In theory it should work most of the time. In practice, you can never be 100% sure as there's always going to be the chance of a dependency or pattern that makes it incompatible. But, that doesn't necessarily mean we shouldn't do it, because those issues would likely also apply to OpenNext apps.

workers-devprod · 2026-08-03T18:46:14Z

Codeowners approval required for this PR:

@cloudflare/wrangler

Show detailed file reviewers

.changeset/c3-next-vinext.md: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/helpers/framework-helpers.ts: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/tests/frameworks/frameworks.test.ts: [@cloudflare/wrangler]
packages/create-cloudflare/e2e/tests/frameworks/test-config.ts: [@cloudflare/wrangler]
packages/create-cloudflare/src/frameworks/package.json: [@cloudflare/wrangler]
packages/create-cloudflare/templates/next/c3.ts: [@cloudflare/wrangler]
packages/create-cloudflare/templates/next/experimental_c3.ts: [@cloudflare/wrangler]

feat(c3): scaffold Next.js apps with vinext instead of OpenNext

62f4790

Point create-cloudflare --framework=next at create-vinext-app so the generated project matches the recommended Next.js-on-Workers path (vinext dev/build + vinext-cloudflare deploy) instead of the OpenNext remote template.

feat(c3): keep OpenNext as an opt-in Next.js variant

d4a4cba

Prompt for vinext (default) vs OpenNext when scaffolding Next.js. --variant=vinext|opennext and -y/--accept-defaults (vinext) cover the non-interactive paths so OpenNext stays one flag away.

irvinebroque requested review from MattieTK and james-elicx July 28, 2026 19:23

scottbuscemi marked this pull request as ready for review July 28, 2026 20:23

scottbuscemi requested a review from workers-devprod as a code owner July 28, 2026 20:23

This comment was marked as resolved.

Sign in to view

fix(c3): use variant-specific Next.js types paths

3d4c22e

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(c3): scaffold Next.js apps with vinext instead of OpenNext - #14896

feat(c3): scaffold Next.js apps with vinext instead of OpenNext#14896
scottbuscemi wants to merge 3 commits into
cloudflare:mainfrom
scottbuscemi:c3-next-use-vinext

scottbuscemi commented Jul 28, 2026 •

edited

Loading

Uh oh!

changeset-bot Bot commented Jul 28, 2026 •

edited

Loading

Uh oh!

scottbuscemi commented Jul 28, 2026

Uh oh!

workers-devprod commented Jul 28, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

ajhawkings commented Jul 31, 2026

Uh oh!

james-elicx commented Aug 1, 2026

Uh oh!

workers-devprod commented Aug 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

scottbuscemi commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Behavior

Changes

Generated project shapes

Notes / follow-ups for reviewers

Uh oh!

changeset-bot Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

scottbuscemi commented Jul 28, 2026

Update: OpenNext kept as an opt-in variant

Uh oh!

workers-devprod commented Jul 28, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

ajhawkings commented Jul 31, 2026

Uh oh!

james-elicx commented Aug 1, 2026

Uh oh!

workers-devprod commented Aug 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

scottbuscemi commented Jul 28, 2026 •

edited

Loading

changeset-bot Bot commented Jul 28, 2026 •

edited

Loading