| Filename | Latest commit message | Latest commit date |
|---|---|---|
8ddab401f9
Step 2 of the nav restructure: make the H0M3 menu hub the landing page at / and move the dashboard SPA to /dashboard.html, with every surface linking back to the hub. Mechanism (frontend-only, no host-side change — confirmed against the ServeDir route table): the dashboard's ServeDir fallback serves index.html at / via append_index_html_on_directories, and there is no SPA path-routing catch-all to break. The dashboard SPA is served as the plain file dashboard.html so it never shadows the exact-match /dashboard/stream + /dashboard/history SSE routes registered before the fallback. - Swap the HTML entry files: the H0M3 page becomes index.html (loads home.js → served at /), and the dashboard SPA becomes dashboard.html (loads tabs.js → served at /dashboard.html). build.mjs copies the new set; JS bundle names are unchanged (referenced by absolute /static/ paths, independent of the HTML filename). - H0M3 Dashboard tile now points at /dashboard.html. - The dashboard gains a "← home" back-link in its chrome; flow.html and logs.html relabel their back-link from "← dashboard" to "← home" (href stays / — which is the hub now). Pages link to the hub, not to each other. - Agent page (app.js + stats.js): the "↑ dashboard" link now targets /dashboard.html. The API base (rebuild / answer-question / mark-all-read POSTs) stays the origin root, unchanged. - Comment-only: tabs.js / flow.js / common.js references to the dashboard's old index.html filename updated to dashboard.html. Note for review: git renders the file swap as a deleted home.html + an added dashboard.html + a heavily-modified index.html, because index.html exists on both sides with swapped content. It's a content swap, not a rewrite — the built dist/ is verified (index.html→home.js, dashboard.html →tabs.js). Deferred to a follow-up: removing the FL0W / L0GS / M4TR1X "→" page-links from the dashboard tab strip (touches tabs.js gating/overflow), and the shared reusable chrome component (a later step). |
||
| .. | ||
| packages | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
hyperhive frontend
npm workspaces project for the hyperhive browser-facing assets:
packages/shared/— shared modules used by both surfaces (terminal pane, Catppuccin palette + body typography).packages/dashboard/— the hive-c0re dashboard SPA.packages/agent/— the per-container web UI (default agent page, stats, screen).
Build
npm install # one-off; uses the checked-in package-lock.json
npm run build # builds every workspace into packages/*/dist/
The Rust binaries serve packages/dashboard/dist/ and
packages/agent/dist/ via tower_http::ServeDir at runtime; the
build derivation is wired up in nix/modules/frontend.nix. Per-agent
additions are layered on top of the default agent dist via the
hyperhive.frontend.extraFiles option in agent.nix.
Why npm + esbuild
- Hermetic: dependencies vendored via the checked-in lockfile;
buildNpmPackagein nix uses it as the source-of-truth so the output is reproducible without network access at build time. - esbuild: vanilla-JS bundler, no framework runtime overhead.
Each workspace's
build.mjsis ~30 lines. - Single-PR migration: see issue #273 for the design proposal and the four-commit shape (npm scaffold → nix derivations → container plumbing → Rust cutover).