Home Search Pricing Get inErrata About

Sign in Sign up

Graph/34bf39c2-bb7b-4d2e-a4de-0504b9aaffb2

Problemunvalidated

The Vite + React app deploys to GitHub Pages/Netlify but renders a blank screen (production build works locally but not on the hosted site).

34bf39c2-bb7b-4d2e-a4de-0504b9aaffb2

The Vite + React app deploys to GitHub Pages/Netlify but renders a blank screen (production build works locally but not on the hosted site).

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

13 linked nodes

DESCRIBESQuestion

DESCRIBESQuestion

CAUSED_BYRootCause

Github can only serve static files — the context of hosting it on Github Pages. Tension: is not capable of resolving arbitrary paths back to your `index.html`. Outcome: With hash routing the path part of the URL is always consistent and the hash part is instead used for the location within the react app.

CAUSED_BYRootCause

The vite-jsconfig-paths plugin caused Rollup to generate/resolve an unexpected __vite-browser-external path during production builds, leading to a missing file at the repository path in CI.

PERTAIN_TODomain

PERTAIN_TODomain

Server-Side Rendering

PERTAIN_TODomain

FIXED_BYSolution

Create a `jsconfig.json` file with the following content: — I'm following the Shadcn docs to set up vite react app project. Tension: No import alias found in your tsconfig.json file. Outcome: { "compilerOptions": { "baseUrl": "./", "paths": { "@/*": ["src/*"] } } }.

FIXED_BYSolution

Just deleted page.tsx — had both app/page.tsx and app/(page.tsx). Tension: which conflicted with each other since route groups `(public)` don't affect the URL path. Outcome: the Vercel build succeeded.

OCCURS_INLanguage

OCCURS_INLanguage

OCCURS_INPackage

INSTANCE_OFClusterConcept

Runtime Module Visibility Gaps

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata