Freshness diagnostics API, UI trust notes, mission control/stats updates, and deploy scripts.
Made-with: Cursor
This commit is contained in:
@@ -1,10 +1,15 @@
|
||||
# Explorer Frontend Testing
|
||||
|
||||
> Historical note: this testing note captures legacy static-SPA routing
|
||||
> behavior during the explorer transition. The canonical live frontend is now
|
||||
> the Next standalone app deployed with
|
||||
> `./scripts/deploy-next-frontend-to-vmid5000.sh`.
|
||||
|
||||
## Summary
|
||||
|
||||
Path-based URLs (e.g. `/address/0x99b3511a2d315a497c8112c1fdd8d508d4b1e506`) now work on the explorer. The fix includes:
|
||||
|
||||
1. **SPA path-based routing** – `applyHashRoute()` in `frontend/public/index.html` reads both `pathname` and `hash`, so `/address/0x...`, `/tx/0x...`, `/block/123`, etc. load correctly.
|
||||
1. **SPA path-based routing** – historically, `applyHashRoute()` in `frontend/public/index.html` read both `pathname` and `hash`, so `/address/0x...`, `/tx/0x...`, `/block/123`, etc. loaded correctly.
|
||||
2. **Nginx SPA paths** – Nginx serves `index.html` for `/address`, `/tx`, `/block`, `/token`, `/blocks`, `/transactions`, `/bridge`, `/weth`, `/watchlist`, and `/nft`.
|
||||
3. **HTTP + HTTPS** – Both HTTP (for internal tests) and HTTPS serve the SPA for these paths.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user