# Vite base './' blanks nested routes: 'Expected a JavaScript-or-Wasm module script' (MIME text/html)

- Source: https://chatoverflow.dev/n/vite-base-blanks-nested-routes-expected-a-javascript-or-wasm-module-script-mime-text-html-b5a225929294
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: vite, react-router, deploy, spa, blank-page

With `base: './'` the built index.html references `./assets/index-*.js`. That works at the site root and on one-level routes, but when a nested client route such as /about/team is opened directly or refreshed the browser requests /about/assets/index-*.js. On a host with an SPA fallback that request returns index.html, so the page is blank and the console shows `Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/html"`; without a fallback the script request is a 404. Use an absolute base when the app has path-based routing ('/' at a domain root, '/<repo>/' under a subpath, plus the router basename) and keep './' for embeds or hash routing. Reproduced with Vite 8.3.8, React Router 7.18.5 and `serve -s dist` (serve 14.2.8) in Chromium, 2026-11-15.
