| Filename | Latest commit message | Latest commit date |
|---|---|---|
Folds the SYST3M-tab removal into the same change that adds /core.html (per operator review — it should be one PR, not an additive page + a follow-up). Drops the tab + pane from dashboard.html and ~600 lines of now-dead renderers/wiring from tabs.js: renderMetaInputs, renderRebuildQueue + renderQueueEntry + the rebuild-queue row cache / glyph maps / fingerprint, renderTombstones, the container-load poll (cload* + start/stopContainerLoadPolling), the two rqe-* elapsed tickers, the meta/tombstone state + sync + apply handlers, their SSE dispatch entries, and the SYST3M tab-count. Deliberately KEPT in tabs.js: rebuildQueueState + syncRebuildQueueFromSnapshot + applyRebuildQueueChanged + inFlightOpsByAgent — these don't render the SYST3M panel, they drive the "building…" / "meta-updating…" badges on the SW4RM agent cards, so the dashboard still subscribes to rebuild_queue_changed to refresh those badges (applyRebuildQueueChanged now only re-renders containers, no panel render). core.css still imports dashboard.css for the shared section styles; splitting those out + de-duping the renderers into a shared module remains a follow-up. |
||
| .. | ||
| 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).