[GH-ISSUE #22] Vinext failes to work on new hello world Next.js app #8

New issue

Closed

opened 2026-05-06 12:36:25 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-06 12:36:25 +02:00

Owner

Originally created by @taeold on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/22

Version

$ node --version
v22.19.0
$ sw_vers
ProductName:            macOS
ProductVersion:         15.7.4
BuildVersion:           24G517

Reproduction Steps

Bootstrap a new Next.js project:

$ npx create-next-app@latest my-app --yes
$ cd my-app

Install and initialize vinext:

$ npm install vinext
$ npx vinext init

  vinext init

  Running compatibility check...


  vinext compatibility report
  ========================================

  Imports: 1/2 fully supported
    ~  next/font/google (1 file) — fonts loaded from CDN, not self-hosted at build time
    ✓  next/image (1 file) — uses @unpic/react (no local optimization yet)

  Libraries: 1/1 compatible
    ✓  tailwindcss

  Project structure:
    ✓  App Router (app/)
    ✓  1 page(s)
    ✓  1 layout(s)

  ----------------------------------------
  Overall: 92% compatible (5 supported, 1 partial, 0 issues)

  Partial support (may need attention):
    ~  next/font/google — fonts loaded from CDN, not self-hosted at build time


  vinext init complete!

    - Skipped vite.config.ts (already exists, use --force to overwrite)

  Next steps:
    npm run dev:vinext    Start the vinext dev server
    npm run dev           Start Next.js (still works as before)

Run the dev server:

$ npm run dev:vinext

> my-app@0.1.0 dev:vinext
> vite dev --port 3001

Failed to resolve dependency: react-server-dom-webpack/server.edge, present in rsc 'optimizeDeps.include'
Failed to resolve dependency: react-server-dom-webpack/client.edge, present in rsc 'optimizeDeps.include'
Failed to resolve dependency: react-server-dom-webpack/client.edge, present in ssr 'optimizeDeps.include'
Failed to resolve dependency: react-server-dom-webpack/client.browser, present in client 'optimizeDeps.include'

  VITE v7.3.1  ready in 331 ms

  ➜  Local:   http://localhost:3001/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
[vite] connected.
1:17:33 PM [vite] Internal server error: Could not resolve "react-server-dom-webpack/server.edge" imported by "@vitejs/plugin-rsc". Is it installed?
      at eval (plugin-rsc:false:1:25)...

Originally created by @taeold on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/22 ## Version ```bash $ node --version v22.19.0 $ sw_vers ProductName: macOS ProductVersion: 15.7.4 BuildVersion: 24G517 ``` ## Reproduction Steps Bootstrap a new Next.js project: ``` $ npx create-next-app@latest my-app --yes $ cd my-app ``` Install and initialize vinext: ```bash $ npm install vinext $ npx vinext init vinext init Running compatibility check... vinext compatibility report ======================================== Imports: 1/2 fully supported ~ next/font/google (1 file) — fonts loaded from CDN, not self-hosted at build time ✓ next/image (1 file) — uses @unpic/react (no local optimization yet) Libraries: 1/1 compatible ✓ tailwindcss Project structure: ✓ App Router (app/) ✓ 1 page(s) ✓ 1 layout(s) ---------------------------------------- Overall: 92% compatible (5 supported, 1 partial, 0 issues) Partial support (may need attention): ~ next/font/google — fonts loaded from CDN, not self-hosted at build time vinext init complete! - Skipped vite.config.ts (already exists, use --force to overwrite) Next steps: npm run dev:vinext Start the vinext dev server npm run dev Start Next.js (still works as before) ``` Run the dev server: ```bash $ npm run dev:vinext > my-app@0.1.0 dev:vinext > vite dev --port 3001 Failed to resolve dependency: react-server-dom-webpack/server.edge, present in rsc 'optimizeDeps.include' Failed to resolve dependency: react-server-dom-webpack/client.edge, present in rsc 'optimizeDeps.include' Failed to resolve dependency: react-server-dom-webpack/client.edge, present in ssr 'optimizeDeps.include' Failed to resolve dependency: react-server-dom-webpack/client.browser, present in client 'optimizeDeps.include' VITE v7.3.1 ready in 331 ms ➜ Local: http://localhost:3001/ ➜ Network: use --host to expose ➜ press h + enter to show help [vite] connected. 1:17:33 PM [vite] Internal server error: Could not resolve "react-server-dom-webpack/server.edge" imported by "@vitejs/plugin-rsc". Is it installed? at eval (plugin-rsc:false:1:25)... ```

BreizhHardware closed this issue

2026-05-06 12:36:25 +02:00

BreizhHardware commented

2026-05-06 12:36:26 +02:00

Author

Owner

@southpolesteve commented on GitHub (Feb 25, 2026):

Fixed in #31. Two things were broken: vinext init wasn't installing react-server-dom-webpack for App Router projects, and react-server-dom-webpack@19.2.4 requires react@^19.2.4 but create-next-app ships react@19.2.3. The fix adds rsdw to the init deps and does a React upgrade step first when the installed version is too old. We also added a CI job that scaffolds a real create-next-app project and verifies vinext init + dev server work end-to-end. Thanks for the detailed repro steps!

@southpolesteve commented on GitHub (Feb 25, 2026): Fixed in #31. Two things were broken: vinext init wasn't installing react-server-dom-webpack for App Router projects, and react-server-dom-webpack@19.2.4 requires react@^19.2.4 but create-next-app ships react@19.2.3. The fix adds rsdw to the init deps and does a React upgrade step first when the installed version is too old. We also added a CI job that scaffolds a real create-next-app project and verifies vinext init + dev server work end-to-end. Thanks for the detailed repro steps!

BreizhHardware referenced this issue

2026-05-06 12:38:44 +02:00

[PR #8] [MERGED] chore: bump version to 0.0.2 #241