[GH-ISSUE #1033] Make create-vinext-app platform-agnostic #228

Open
opened 2026-05-06 12:38:21 +02:00 by BreizhHardware · 0 comments

Originally created by @Divkix on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/1033

Right now create-vinext-app scaffolds every project with @cloudflare/vite-plugin, a wrangler.jsonc, and a worker/index.ts entry point. It only does Cloudflare Workers, end to end.

The main README says vinext works everywhere — Nitro, Node standalone, you name it — but the scaffolding tool doesn't give you any of those options. That gap is worth closing.

What needs to happen:

  • Platform selection in the CLI — probably a prompt or a --platform flag. Default stays Workers (it's the smoothest path), but allow picking nitro, standalone (Node), or none for just a bare Vite config.
  • Template variants per platform — Workers templates keep what they have now (Cloudflare plugin, wrangler, worker entry). Nitro templates swap the Cloudflare plugin for nitro/vite and drop wrangler. Standalone just runs vinext with no platform plugin.
  • Keep templates simple — no combinatorial explosion. A small set of composable sub-templates (platform-specific config + entry) that get layered over the shared app source is better than full template duplication.
  • Update the README — right now it says "optimized for Cloudflare Workers" everywhere. Should reflect that Workers is one option among several.

References:

  • PR that introduced create-vinext-app: #1032
  • Original tracking issue for the CLI: #407

This can land in a follow-up PR after #1032 merges.

Originally created by @Divkix on GitHub (May 3, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/1033 Right now `create-vinext-app` scaffolds every project with `@cloudflare/vite-plugin`, a `wrangler.jsonc`, and a `worker/index.ts` entry point. It only does Cloudflare Workers, end to end. The main README says vinext works _everywhere_ — Nitro, Node standalone, you name it — but the scaffolding tool doesn't give you any of those options. That gap is worth closing. What needs to happen: - **Platform selection in the CLI** — probably a prompt or a `--platform` flag. Default stays Workers (it's the smoothest path), but allow picking `nitro`, `standalone` (Node), or `none` for just a bare Vite config. - **Template variants per platform** — Workers templates keep what they have now (Cloudflare plugin, wrangler, worker entry). Nitro templates swap the Cloudflare plugin for `nitro/vite` and drop wrangler. Standalone just runs vinext with no platform plugin. - **Keep templates simple** — no combinatorial explosion. A small set of composable sub-templates (platform-specific config + entry) that get layered over the shared app source is better than full template duplication. - **Update the README** — right now it says "optimized for Cloudflare Workers" everywhere. Should reflect that Workers is one option among several. References: - PR that introduced `create-vinext-app`: #1032 - Original tracking issue for the CLI: #407 This can land in a follow-up PR after #1032 merges.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vinext#228
No description provided.