[GH-ISSUE #312] Creating and deploying a new project is broken #73

Closed
opened 2026-05-06 12:37:00 +02:00 by BreizhHardware · 0 comments

Originally created by @sandervspl on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/312

These were the steps I took (straight from your readme)

  1. npm create next-app@latest
  2. npx vinext init

Then I tried to deploy.

Issues that I encountered that were not specified in the readme:

  1. I needed a CLOUDFLARE_API_TOKEN. Sure. But what permissions? I went with "edit workers" template. Please make this more clear in the readme
  2. API error reaching /memberships -> I needed to add my account ID to wrangler.jsonc. I only found out after googling this error. This step is missing in the readme
  3. Build failed: Could not resolve "virtual:vinext-rsc-entry". Had to ask AI for this one. It updated my vite.config.ts file to this
import vinext from "vinext";
import { defineConfig } from "vite";
import { cloudflare } from "@cloudflare/vite-plugin";

export default defineConfig({
  plugins: [
    vinext(),
    cloudflare({
      viteEnvironment: { name: "rsc", childEnvironments: ["ssr"] },
    }),
  ],
});

After that, my deploy finally worked.

I don't know if all of this is the recommended path, so I won't make a PR. But please make the initial deploy docs better ❤️

Originally created by @sandervspl on GitHub (Mar 7, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/312 These were the steps I took (straight from your readme) 1. `npm create next-app@latest` 2. `npx vinext init` Then I tried to deploy. Issues that I encountered that were not specified in the readme: 1. I needed a CLOUDFLARE_API_TOKEN. Sure. But what permissions? I went with "edit workers" template. **Please make this more clear in the readme** 2. `API error reaching /memberships` -> I needed to add my account ID to wrangler.jsonc. I only found out after googling this error. **This step is missing in the readme** 3. Build failed: Could not resolve "virtual:vinext-rsc-entry". Had to ask AI for this one. It updated my `vite.config.ts` file to this ```ts import vinext from "vinext"; import { defineConfig } from "vite"; import { cloudflare } from "@cloudflare/vite-plugin"; export default defineConfig({ plugins: [ vinext(), cloudflare({ viteEnvironment: { name: "rsc", childEnvironments: ["ssr"] }, }), ], }); ``` After that, my deploy finally worked. I don't know if all of this is the recommended path, so I won't make a PR. But please make the initial deploy docs better ❤️
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#73
No description provided.