| Filename | Latest commit message | Latest commit date |
|---|---|---|
Follow-up to the route swap (#1501): now that every separate page is reachable from the H0M3 hub, the dashboard tab strip should hold only real in-page tabs, not the "→" links out to other pages (mara: "remove links to the pages from dashboard - only actual tabs stay here"). - dashboard.html: remove the `tab-matrix`, `tab-flow`, and `tab-logs` `.tab-link` entries (and the stale `tab-count-flow` pill slot — the operator inbox moved to Y3R C4LL). The dashboard strip is now SW4RM / Y3R C4LL / SYST3M / P3RM1SS10NS / SCH3DUL3S / P33RS / ST4TS / S3TT1NGS. - tabs.js: drop the now-dead `tab-matrix` matrix_gui_enabled gate (the H0M3 Matrix tile is gated by home.js instead) and the obsolete `#tab-count-flow` comment. Kept the contextual deep-links into the log viewer (an agent's logs, a build entry's log) — those are functional content links, not navigation chrome. - flow.css: remove the dead `.dashboard-chrome.flow-chrome` + `.tabbar .tab.active.tab-link` rules — the flow page uses a slim back-link header, not the dashboard tabbar, and `.tab-link` no longer exists anywhere. npm run build green (flow.css 1.8kb). No residual references. |
||
| .. | ||
| 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).