fix: revert base path after dedicated funnel (#7) #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "7-revert-base-path"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Remove
base: '/svelte/'from vite.config.js and replace all/svelte/path prefixes with/across 8 source files. The dedicated Tailscale funnel (pal-e-deployments PR #49) serves content from root, eliminating the need for subpath hacks.Changes
vite.config.js-- removedbase: '/svelte/'(reverts to default/)index.html-- replaced 3/svelte/prefixed links with/westside/staff.html-- replaced 16/svelte/references in nav, links, asset pathswestside/sponsors.html-- replaced 13/svelte/referenceswestside/success.html-- replaced 12/svelte/referenceswestside/index.html-- replaced 5/svelte/references in OG/Twitter/favicon meta tagswestside/Nav.svelte-- replaced 7/svelte/references in nav linkswestside/App.svelte-- replaced 1/svelte/reference in FAQ staff linkTest Plan
npm run buildsucceeds with no errorsgrep -r '/svelte/' dist/returns zero matches/svelte/path references remain in source fileshttps://svelte-playground.tail5b443a.ts.net/serves hub pagehttps://svelte-playground.tail5b443a.ts.net/westside/serves westside prototypeReview Checklist
Dependency
DO NOT MERGE until pal-e-deployments PR #49 is merged and applied. That PR creates the dedicated Tailscale funnel. Without it, reverting the base path will break all links since the content would still be served under
/svelte/on the shared playground.Merge order:
cd ~/svelte-playground && npm run buildcurl https://svelte-playground.tail5b443a.ts.net/Related
Review: LGTM
Files reviewed: 8 (8 modified)
Findings: None.
base: '/svelte/'removed from vite.config.js -- Vite defaults to//svelte/path references replaced with/across 8 filesnpm run buildsucceeds cleanlygrep -r '/svelte/' dist/returns zero matches in build output/svelte/path references (onlypackage-lock.jsonnpm registry URL, which is correct)PR #9 Review
DOMAIN REVIEW
Tech stack: Vite + Svelte 5, static HTML pages, vanilla CSS. This is a playground/prototype repo -- no backend, no auth, no database.
Change summary: Pure find-and-replace of
/svelte/path prefix to/across 8 files (1 config + 7 source files). This reverts thebase: '/svelte/'workaround in vite.config.js now that svelte-playground has its own dedicated Tailscale funnel (pal-e-deployments PR #49).Diff analysis (57 additions, 58 deletions across 8 files):
vite.config.js-- removedbase: '/svelte/'line (net -1 line, correct)index.html-- 3 path replacements in nav brand + project card linkswestside/index.html-- 5 replacements in OG/Twitter/favicon meta tagswestside/staff.html-- 16 replacements in meta tags, nav, coach photosrcattributeswestside/sponsors.html-- 13 replacements in meta tags, nav, sponsor imageswestside/success.html-- 12 replacements in meta tags, nav, back-to-home linkwestside/Nav.svelte-- 7 replacements in nav brand logo + nav linkswestside/App.svelte-- 1 replacement in FAQ staff linkCompleteness check: Verified via grep that zero
/svelte/path references remain in any.html,.svelte,.js, or.csssource files after this change. The only match in the entire repo is the npm registry URL inpackage-lock.json, which is correct and unrelated.Files NOT touched that could contain references:
westside/Footer.svelteandpal-e-app/board.sveltewere verified -- neither contains/svelte/path references. Clean.Correctness: Every replacement is a mechanical
/svelte/footo/foosubstitution. No logic changes, no structural changes, no new code. The transformation is consistent and complete.BLOCKERS
None.
NITS
DRY observation (pre-existing, not introduced by this PR): The navigation markup is duplicated across
staff.html,sponsors.html, andsuccess.html-- identical nav bars copied verbatim. The SvelteNav.sveltecomponent already exists and handles this for the SPA entry point, but the static HTML pages duplicate it. This is a known trade-off of multi-page playground architecture and not in scope for this fix PR. Noting for future consideration only.Dependency gate is well-documented: The PR body clearly states "DO NOT MERGE until pal-e-deployments PR #49 is merged and applied" with a numbered merge order. Good practice.
SOP COMPLIANCE
7-revert-base-pathreferences issue #7Closes #7, cross-repo dependencyforgejo_admin/pal-e-deployments#49documentedPROCESS OBSERVATIONS
grep -r '/svelte/' dist/). The test plan includes both pre-deploy verification (build + grep) and post-deploy smoke tests.VERDICT: APPROVED