fix: properly separate static pages from Vite-built React pages #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.




Summary
Fixes the webapp to properly serve the landing page instead of the Vite React shell.
Problem
The webapp was serving the Vite build output (
dist/index.html- "Worlddriven Admin") instead of the actual landing page (public/index.html).Solution
Properly separate static pages from Vite-processed React pages:
Static pages (served directly from
public/):index.html)React pages (Vite entry points, built to
dist/):Changes
rollupOptions.inputfor multi-page apppublicDir: falseso Vite doesn't copy/overwrite public filespublic/, React fromdist/Architecture
Test Plan