Confirm the final public base path and whether a frontend router is used. Keep the build output separate from the source project and private configuration.

1. Set the Vite public base option to the intended deployment path before building. Use the appropriate documented relative-base behavior only when that is the planned architecture.

2. Configure the client router’s base or basename consistently. A correct asset prefix does not automatically change the router’s own URL assumptions.

3. Build the project with its locked dependencies and publish the generated output into the matching server directory.

4. Configure a fallback for application routes under that path where required. Exclude existing assets and unrelated API or website paths from the fallback.

5. Test the entry page, a nested route, a browser refresh and navigation back to the parent website.

For a site published at https://example.com/portal/, merge this base-path setting into the existing Vite configuration before the production build. Keep other plugins and project settings in place.

import { defineConfig } from 'vite';

export default defineConfig({
  base: '/portal/',
});

Deploy the generated dist contents into the matching portal document directory. If the application has a browser router, configure its base or basename separately to agree with the same path. A server rewrite can support direct route visits, but it cannot repair asset addresses already built with the wrong prefix.

Expected result: The browser requests JavaScript and CSS below /portal/, and a direct visit to a supported inner route works. A missing asset still fails normally, while the parent website at / keeps its own routing and content.

Inspect CSS and JavaScript requests and confirm they use the intended prefix. Check that an unknown asset is not returned as the application HTML with an incorrect content type.

If the page is blank, distinguish missing assets from a router error. Review the browser console and network responses before changing the server’s main document root.

• Making client-side routes work after a browser refresh
• Building a deployment artifact in CI
• Hosting a React website: static builds and server-rendered applications
• Deploying a Nuxt Node server build

• Vite production build
• Vite shared base option