I noticed a curious case where, when vite generates files that are foo-blah.extension, the files are served with the wrong mime type. For example assets/index-424242.js is served with mime-type text/html. What I do is build + package somewhere else (in CI) and then use

npx wrangler pages publish build --project-name=

to deploy to CF. Reading the forums it seems that many others have stumbled on the same problem 2021 and 2022 without it getting fixed, it seems. So I added a _headers file which overrides the content-type for

/*.js

and

/*.css

correctly because modern browsers tend to be picky and they do not want to execute .js files unless the mime type is correctly set. This part works but it is really annoying to have to do that. While troubleshooting this, I noticed an even curiouser case where if I request /index.html I get the file as one would expect, but if I request /assets/index-424242.js I get, instead of the uploaded javascript, file the contents of the top level index.html instead. This obviously breaks everything. Now, as I build elsewhere, I can prove (to myself) that vite+swc built everything correctly and that there really is a 4.5 MB assets/index-424242.js file in the build root. If I deploy the static javascript stuff to a regular nginx instance anywhere I get the correct files and that's that. Recap: - I build and package outside CF - I use wrangler to upload - There aren't any functions, I have assumed pages.dev is simply a place that serves files that were uploaded there - The entire site consists of html, js, svg, css assets Any ideas on where to start? Any pointers welcome, of course...

When you visit a file and get served the root index.html, that means the file can't be found, and it defaults to your 404.html if present, or index.html if not

thanks, suddenly everything makes sense 😉