[GH-ISSUE #459] vinext start fails: "RSC entry does not export a default handler function" #104

New issue

Closed

opened 2026-05-06 12:37:14 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-06 12:37:14 +02:00

Owner

Originally created by @skyblue on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/459

Summary

After a successful vinext build, running vinext start fails with:

[vinext] RSC entry does not export a default handler function

Repro

npm run build
vinext start

Actual

vinext start exits with the error above.

Expected

vinext start should work with the build output, or provide a clear message that this target must be run with Wrangler.

Observed output shape

dist/server/index.js default export is a Worker-style object ({ fetch() {} }), not a function.

Environment

macOS
vinext 0.0.27
vite 7.3.1
wrangler 4.72.0
next 16.1.6
react/react-dom 19.2.4

Workaround

Use Wrangler to run the built output:

wrangler dev --config dist/server/wrangler.json --port 3000 --local --test-scheduled=false

Originally created by @skyblue on GitHub (Mar 11, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/459 ## Summary After a successful `vinext build`, running `vinext start` fails with: ```text [vinext] RSC entry does not export a default handler function ``` ## Repro 1. `npm run build` 2. `vinext start` ## Actual `vinext start` exits with the error above. ## Expected `vinext start` should work with the build output, or provide a clear message that this target must be run with Wrangler. ## Observed output shape `dist/server/index.js` default export is a Worker-style object (`{ fetch() {} }`), not a function. ## Environment - macOS - vinext 0.0.27 - vite 7.3.1 - wrangler 4.72.0 - next 16.1.6 - react/react-dom 19.2.4 ## Workaround Use Wrangler to run the built output: ```bash wrangler dev --config dist/server/wrangler.json --port 3000 --local --test-scheduled=false ```