| Filename | Latest commit message | Latest commit date |
|---|---|---|
mara's review nit: explaining the absence of a manager special-case implicitly endorses the idea that special cases would be normal. Default is no special case; the doc shouldn't dwell on it. - ST0P comment block removed entirely (the bulk-button line above is self-explanatory; the substantive 'c0re survives manager-down' rationale lives in the host docs, not here). - M0V3 helper comment reframed: trim the 'no special-case' framing but keep the substantive note that the backend refuses moves it can't satisfy and the failure surfaces in the bulk roll-up. - docs/web-ui.md::Selection bar bullet list: drop the 'manager included; no special-case' qualifiers; just describe the action. M0V3→ROOT keeps the rationale that backend refusals surface in the roll-up but stops calling out manager specifically. |
||
| .. | ||
| 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).