Vercel Env Checker

Vite base path preflight

Check Vite base before GitHub Pages assets 404.

Paste static config and path snippets. The checker compares the expected subpath, configured base, public asset paths, absolute links, and router basename clues without running your project.

No GitHub loginNo build executionStatic paths only

Deploy target

Config only
No repo access. This page checks static Vite config fields only. Do not paste tokens, private deployment logs, or full source files.
fail

Base path result

fail

Fix the blocking base path issues before deploying this Vite build.

Expected base/portfolio-site/
Configured base/
/public paths1
Root links3
critical

Configured base does not match the target path

The config uses "/", but this target expects "/portfolio-site/".

  • Use base: "/portfolio-site/" for this deploy target, then rebuild before uploading dist.
critical

Public asset paths include /public

/public/logo.svg will not match Vite public asset URLs after build.

  • Reference public files from the site root, such as /logo.svg, and let base handling happen at build time.
warning

Root-absolute links may bypass the subpath

/public/logo.svg, /about, /src/main.tsx start at the domain root instead of the deployed subpath.

  • For app links, use router links with the matching basename or build URLs from import.meta.env.BASE_URL.

Detected path clues

Root-absolute links

/public/logo.svg/about/src/main.tsx

Router basenames

none

Copyable report

Vite base path preflight
Status: fail
Expected base: /portfolio-site/
Configured base: /

Findings:
- [critical] Configured base does not match the target path
  Use base: "/portfolio-site/" for this deploy target, then rebuild before uploading dist.
- [critical] Public asset paths include /public
  Reference public files from the site root, such as /logo.svg, and let base handling happen at build time.
- [warning] Root-absolute links may bypass the subpath
  For app links, use router links with the matching basename or build URLs from import.meta.env.BASE_URL.

Public /public/ paths: 1
Root-absolute path clues: 3
Router basename clues: none

Boundary: static config/path check only. It does not connect to GitHub, inspect private repositories, or run Vite.

What this checks

It checks Vite `base`, GitHub Pages project subpaths, public asset URL mistakes, root-absolute links, and SPA router basename clues.

What this does not do

It does not run Vite, fetch private assets, connect to GitHub, read repository files, or guarantee a deployment is production-ready.