5.2 — /home (alt route): renders coherently; does not 404, does not duplicate-render the primary home. #199
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#199
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
For 5.2 —
/homealt route, this is a Fail. @PlasticDigitsIt does not 404, but it also does not render coherently. The page only shows the green background/grid and no homepage content/cards.
Checklist Item: 5.2
Section: Routing /
/homealt routeStatus: Fail
Device/Viewport: Desktop
Wallet State: Not required
Steps: Opened
http://localhost:5176/homedirectly in the browser.Expected Result:
/homeshould render coherently and should not duplicate-render the primary home.Actual Result:
/homeloads a blank green background/grid with no visible homepage content. It does not show a 404, but the route content does not render properly.Evidence: Screenshot provided.
Notes: This appears to be a broken/empty alt route state.
changed the description
changed title from
/home alt route renders blank page instead of coherent homepage content`to5.2 — /home (alt route): renders coherently; does not 404, does not duplicate-render the primary home.I think "5.15 — 404 / global error pages match brand and offer recovery paths (home, support)." is connected to this because when going to an 404 page it doesn't show an home page path
mentioned in commit 9e478ef4e2b17fbf0934dd15facc1e37d3e6632c
Update (GitLab #199 —
/homehub route)Root cause: With
VITE_LAUNCH_TIMESTAMPunset (no-env / default dev),ROUTES_NO_ENVonly mountedHomePageon the index route (/). Navigating to/homematchedRootLayoutbut no child route, so<Outlet />stayed empty — shell + green grid, no hero/cards.Fix: Register
path: "home"with the same lazyHomePageinROUTES_NO_ENV(hub alias; canonical URL remains/). Post-launch routing (/→ TimeCurve Simple,/home→ hub) is unchanged.Merged:
main@1e6d3eb(includes merge offix/gitlab-199-home-route-no-env).Docs / invariants
INV-FRONTEND-199-HOME-ROUTE— invariantsdocs/frontend/timecurve-views.md— LaunchCountdown → Simple handoffskills/README.md+.cursor/skills/yieldomega-guardrails/SKILL.mdVerification checklist (for QA)
VITE_LAUNCH_TIMESTAMPin env → open/home→ YieldOmegah1, hero image, Open TimeCurve CTA, surface cards (not blank main)./shows the same hub content as/home; only oneRootLayout(no duplicated chrome).VITE_LAUNCH_TIMESTAMPin the past →/is TimeCurve Simple,/homestill shows full hub.cd frontend && VITE_WALLETCONNECT_PROJECT_ID=test npm run build && npx playwright test e2e/launch-countdown.spec.ts e2e/home.spec.ts(no-env build exercises/homeinno-env routingtest).Requesting verification from @nullvector_ux — please re-run checklist item 5.2 on a fresh
npm run devwith no launch timestamp. Issue stays open until you sign off./cc @PlasticDigits
Verification checklist (for QA) @PlasticDigits
No-env dev: No
VITE_LAUNCH_TIMESTAMPin env → open/home→ YieldOmegah1, hero image, Open TimeCurve CTA, surface cards (not blank main).No-env dev:
/shows the same hub content as/home; only oneRootLayout(no duplicated chrome).Post-launch build (optional):
VITE_LAUNCH_TIMESTAMPin the past →/is TimeCurve Simple,/homestill shows full hub.(skip) Automated:
cd frontend && VITE_WALLETCONNECT_PROJECT_ID=test npm run build && npx playwright test e2e/launch-countdown.spec.ts e2e/home.spec.ts(no-env build exercises/homeinno-env routingtest).Reason: Unfortunately I run to some error and I couldn't automate it
ERROR: Playwright does not support chromium on ubuntu26.04-x64
mentioned in commit
e60ccb3e71@nullvector_ux Please open a new issue for the playwright bug, but closing this issue
mentioned in issue #223