| Filename | Latest commit message | Latest commit date |
|---|---|---|
mara reported the rail still didn't make dependencies visible (screenshot on the PR). Root cause: the rail spans by sibling-array position, but a sibling with its own nested subtree renders many pixel-rows for one array slot -- in a real queue (agent_window with 7-ish children between two top-level siblings), the "line" breaks into disconnected ticks around every real subtree, never reading as a connection at all. My verification fixtures never tested a nested subtree sitting between two related siblings, so this never showed up before. Replaced with a "waits on: <label>" text line under the dependent node, resolved once in buildTree via a global id lookup (not scoped to siblings, so a label still resolves even if a dep ever does cross a group boundary despite the product decision that it shouldn't). Text has no positional-gap failure mode: it's legible regardless of how tall the node above or below it renders. No reordering, no rail, no interleaving-of-independent-pairs class of bug possible anymore -- this is close to the original design proposed on the issue before the heavier visual version was tried. Re-verified against 6 fixture checks including the exact shape from the screenshot (a dependency target with its own nested subtree rendered between it and the dependent node). |
||
| .. | ||
| 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).