[GH-ISSUE #874] Suspense streaming doesn't seem to work with `wrangler dev` #194

New issue

Closed

opened 2026-05-06 12:38:02 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

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

Owner

Originally created by @LubomirGeorgiev on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/874

When I run my vinext app with vinext dev the Suspense blocks get resolved and I can see the initial fallback which is correct.

However if I build the app and run it with wrangler dev the longest suspense promise hangs the whole page and the fallback is never visible.

I made a reproduction repo here https://github.com/LubomirGeorgiev/vinext-next-safe-action

To reproduce it with the correct behaviour run pnpm dev and open http://localhost:3000/
To reproduce the wrong behaviour run pnpm preview and open http://localhost:8787/

Originally created by @LubomirGeorgiev on GitHub (Apr 23, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/874 When I run my vinext app with `vinext dev` the Suspense blocks get resolved and I can see the initial fallback which is correct. However if I build the app and run it with `wrangler dev` the longest suspense promise hangs the whole page and the fallback is never visible. I made a reproduction repo here https://github.com/LubomirGeorgiev/vinext-next-safe-action To reproduce it with the correct behaviour run `pnpm dev` and open http://localhost:3000/ To reproduce the wrong behaviour run `pnpm preview` and open http://localhost:8787/

BreizhHardware closed this issue

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

BreizhHardware commented

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

Author

Owner

@southpolesteve commented on GitHub (Apr 24, 2026):

Thanks for the reports! I suspect this may be the same root issue https://github.com/cloudflare/workers-sdk/issues/8004

@southpolesteve commented on GitHub (Apr 24, 2026): Thanks for the reports! I suspect this may be the same root issue https://github.com/cloudflare/workers-sdk/issues/8004

BreizhHardware commented

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

Author

Owner

@LubomirGeorgiev commented on GitHub (Apr 24, 2026):

@southpolesteve I just deployed it here https://vinext-nextjs.lubomirgeorgievgeorgiev.workers.dev/ and it works fine, so if this is just an issue with wrangler dev I guess it's not so critical.

Btw does that mean that wrangler dev and the cloudflare worker production environment don't run the exact same runtime underneath and it's possible that one thing could work locally but not when deployed and vice versa?

@LubomirGeorgiev commented on GitHub (Apr 24, 2026): @southpolesteve I just deployed it here https://vinext-nextjs.lubomirgeorgievgeorgiev.workers.dev/ and it works fine, so if this is just an issue with `wrangler dev` I guess it's not so critical. Btw does that mean that `wrangler dev` and the cloudflare worker production environment don't run the exact same runtime underneath and it's possible that one thing could work locally but not when deployed and vice versa?

BreizhHardware commented

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

Author

Owner

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

They both use the same runtime: https://github.com/cloudflare/workerd. You should not expect any difference between local and production. If you see the attached wranglerissue it just seems that under wrangler dev it buffers larger chunks which causes issues. The team is looking into a fix.

@southpolesteve commented on GitHub (Apr 25, 2026): They both use the same runtime: https://github.com/cloudflare/workerd. You should not expect any difference between local and production. If you see the attached wranglerissue it just seems that under wrangler dev it buffers larger chunks which causes issues. The team is looking into a fix.

BreizhHardware commented

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

Author

Owner

@LubomirGeorgiev commented on GitHub (Apr 25, 2026):

Thanks

@LubomirGeorgiev commented on GitHub (Apr 25, 2026): Thanks

BreizhHardware referenced this issue

2026-05-06 12:39:30 +02:00

[PR #194] [MERGED] fix: add React version check to vinext build (#185) #379