| Filename | Latest commit message | Latest commit date |
|---|---|---|
8786f24111
Three things from mara's PR review + argus's: - "the info from main list should be included in the agent view" - detail panel now repeats status/message/wanted alongside the panel-only fields (hive, config PR, matrix link), not just the leftovers. - "destroy is already available via wanted state" - dropped the standalone "destroy agent" button; the detail panel's wanted field is a real WantedMenu (default showDestroy) instead, same control as the card/table, just with the fourth option back. Also resolves argus's stale-doc-comment finding (the comment described a second WantedMenu call site that didn't exist yet - now it does). - Rebased onto main to pick up the just-merged dropdown-portal-clip fix - this branch was cut before that merged, so it had silently regressed back to the pre-fix Dropdown the whole time. That rebase surfaced a real bug of its own, likely "the third screenshot shows a layout bug": WantedMenu always passed `portal` to Dropdown, and a portaled (position: fixed, body-appended) dropdown renders *behind* an open native <dialog> - the dialog is promoted to the browser's top layer, which composites above ordinary body content regardless of z-index. Only the sliver of the dropdown extending past the dialog's own edge was visible. WantedMenu's `portal` is now its own prop, opt-in, true only at the table's call site (the one with an actual clipping ancestor to escape) - card and detail-panel call sites render it as a plain child instead, which is both correct inside the dialog and one fewer moving part where it isn't needed. Verified with real CDP clicks: detail panel shows all fields, and its wanted dropdown now renders in the right place with all four options visible instead of mostly hidden behind the dialog. |
||
| .. | ||
| packages | ||
| .gitignore | ||
| npm-deps-hash | ||
| 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/packages/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 the tracked design proposal and the four-commit shape (npm scaffold → nix derivations → container plumbing → Rust cutover).