d-bis/explorer-monorepo
4
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Freshness diagnostics API, UI trust notes, mission control/stats updates, and deploy scripts.

Browse Source 
Made-with: Cursor
This commit is contained in:
defiQUG
2026-04-12 06:33:54 -07:00
parent 0972178cc5
commit 3fdb812a29
63 changed files with 5163 additions and 826 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/EXPLORER_LOADING_TROUBLESHOOTING.md
View File

@@ -1,5 +1,9 @@
# Explorer "Loading…" / "—" Troubleshooting
> Historical note: parts of this troubleshooting guide still refer to the old
> static-SPA deployment path. The current production frontend is the Next
> standalone app deployed with `./scripts/deploy-next-frontend-to-vmid5000.sh`.
When **`/api/v2/stats`** returns 200 with data but the SPA still shows "—" or "Loading blocks…" / "Loading transactions…" / "Loading bridge data…" / "Tokens: Loading…", the failure is in **frontend→API wiring** or **frontend runtime**.
## Expected UI (screenshots)
@@ -71,13 +75,13 @@ After editing `frontend/public/explorer-spa.js`, redeploy the frontend to VMID 5
```bash
# From repo root (with SSH to r630-02)
EXPLORER_VM_HOST=root@192.168.11.12 bash explorer-monorepo/scripts/deploy-frontend-to-vmid5000.sh
EXPLORER_VM_HOST=root@192.168.11.12 bash explorer-monorepo/scripts/deploy-next-frontend-to-vmid5000.sh
```
Or from the Proxmox host that runs VMID 5000:
```bash
/path/to/repo/explorer-monorepo/scripts/deploy-frontend-to-vmid5000.sh
/path/to/repo/explorer-monorepo/scripts/deploy-next-frontend-to-vmid5000.sh
```
Then hard-refresh the explorer (Ctrl+Shift+R / Cmd+Shift+R) and re-check Console + Network.