Hotfix: Use HashRouter for GitHub Pages#2
Merged
Conversation
- Changed from BrowserRouter to HashRouter - Required for GitHub Pages deployment (client-side routing) - Prevents blank page on deployed site - Fixes root path routing issue Critical hotfix for v0.0.1 deployment
AH316
force-pushed
the
hotfix/hash-router-github-pages
branch
from
f84f591 to
0d01da5
Compare
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
1 participant
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.
Problem
Deployed site shows blank gradient - routing is broken on GitHub Pages.
Root Cause
Main branch still has
BrowserRouterwhich doesn't work with GitHub Pages client-side routing.Solution
BrowserRoutertoHashRouterin src/App.tsxTesting
base: './'Impact
Critical hotfix - site is currently non-functional in production
🤖 Generated with Claude Code