Fix Vercel SPA routing with rewrite config#29
Closed
MelonChicken wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
vercel.jsonto support client-side routing on Vercel.index.htmlso React Router can handle page navigation.Why
When users directly access or refresh routes like
/shop,/login, or/archive, Vercel tries to find those paths as real server files and returns404 NOT_FOUND.This rewrite ensures that Vercel serves the frontend app first, and then React Router handles the route internally.
Changes
vercel.json{ "rewrites": [ { "source": "/(.*)", "destination": "/index.html" } ] }How to Test
/shop,/login, or/archive.404 NOT_FOUND.