[GH-ISSUE #232] Getting 404 in build version #55

New issue

Closed

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

BreizhHardware commented

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

Owner

Originally created by @kingRayhan on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/232

I just boot up a fresh Vinext to play with it. It was working in dev, but I was getting 404s in the build version.

https://github.com/user-attachments/assets/e03c7b97-205b-490a-bf19-afebb24bf73c

Originally created by @kingRayhan on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/232 I just boot up a fresh Vinext to play with it. It was working in dev, but I was getting 404s in the build version. https://github.com/user-attachments/assets/e03c7b97-205b-490a-bf19-afebb24bf73c

BreizhHardware closed this issue

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

BreizhHardware commented

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

Author

Owner

@WuMingDao commented on GitHub (Mar 3, 2026):

Hi, I to this question for fun, you offect your project link of github?

@WuMingDao commented on GitHub (Mar 3, 2026): Hi, I to this question for fun, you offect your project link of github?

BreizhHardware commented

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

Author

Owner

@southpolesteve commented on GitHub (Mar 5, 2026):

Will take a look and see if I can reproduce. Haven't tested a ton with Bun yet so might be the issue. Does swapping to node fix it?

@southpolesteve commented on GitHub (Mar 5, 2026): Will take a look and see if I can reproduce. Haven't tested a ton with Bun yet so might be the issue. Does swapping to node fix it?

BreizhHardware commented

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

Author

Owner

@southpolesteve commented on GitHub (Mar 7, 2026):

Thanks for the report! I tried reproducing this with both Node and Bun across several setups (fresh app with published vinext@0.0.23, monorepo fixtures, App Router, Pages Router) and wasn't able to get 404s in the production build. Everything returned 200 as expected.

To help debug this, could you provide:

A git repo that reproduces the problem (ideal, even if it's just a minimal app with a couple pages)
Your package.json, vite.config.ts, and next.config.* (if you have one)
Bun version (bun --version)
OS

A reproducible repo would be the fastest path to figuring this out.

@southpolesteve commented on GitHub (Mar 7, 2026): Thanks for the report! I tried reproducing this with both Node and Bun across several setups (fresh app with published vinext@0.0.23, monorepo fixtures, App Router, Pages Router) and wasn't able to get 404s in the production build. Everything returned 200 as expected. To help debug this, could you provide: - A git repo that reproduces the problem (ideal, even if it's just a minimal app with a couple pages) - Your `package.json`, `vite.config.ts`, and `next.config.*` (if you have one) - Bun version (`bun --version`) - OS A reproducible repo would be the fastest path to figuring this out.

BreizhHardware commented

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

Author

Owner

@southpolesteve commented on GitHub (Mar 7, 2026):

Closing for now since we can't reproduce. Feel free to reopen if you have a reproduction repo or the additional info mentioned above!

@southpolesteve commented on GitHub (Mar 7, 2026): Closing for now since we can't reproduce. Feel free to reopen if you have a reproduction repo or the additional info mentioned above!

BreizhHardware referenced this issue

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

[PR #55] [MERGED] ci: notify Google Chat on npm publish #274