Skip to content

Allow Vite to serve from pages other than index.html #5547

@steveworkman

Description

@steveworkman

Clear and concise description of the problem

As a developer using Vite I want to be able to serve from different HTML pages so that I may more closely replicate my production environment.

I have an application that once built produces two different index.html pages for two different brands, for example index-a.html and index-b.html.

The production web server then chooses which of these html files to serve in SPA mode based on the domain that the request is coming from, so www.example.com goes to index-a.html and www.test.com goes to index-b.html

I'm trying to replicate this with the vite dev server, but I can't because the served page is hard-coded as index.html which you can see in the spaFallback middleware.

I've attempted to override this using a plugin and middleware, but I either get into an infinite redirection loop, or the server never serves the request.

This is not the same as multi-page apps as the target here is SPAs and even with a multi-page app you still need an index.html file in the root of the project. It is also not the same as being able to change the directory that the page is served from - the issue is being able to serve from a file other than index.html.

Suggested solution

Add a configuration property: server.indexFile with a default of index.html that is then used by the vite:spa-fallback module to retrieve the right index file. This should also be able to be set from the command line in the vite serve and vite preview commands.

This should not interfere with the multi-page app setup

Alternative

I've attempted to do this with a plugin, but I don't believe that I can effectively override the vite:spa-fallback middleware.

Additional context

Previously asked in the Discussions area with no positive response.

Validations

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions