| Filename | Latest commit message | Latest commit date |
|---|---|---|
mara, live, on the 500px screenshot: 'does not overflow properly.' Real cause: .agent-header-pills had flex-shrink: 0 (fine for app.js's 2-3-small-pills case, which never needed to shrink) — once badges joined that column last round, that told the flex layout 'give this its full natural unwrapped width no matter what', so once that width exceeded the viewport it just overflowed past the edge instead of ever getting narrow enough to trigger its own flex-wrap. Dropping flex-shrink: 0 (default 1) is the fix. Tried pairing it with min-width: 0 first — made it worse. An unset min-width still floors shrinking at the container's own min-content (the widest single wrapped child, e.g. one badge — a reasonable floor); min-width: 0 removes that floor entirely, so the container shrinks past what its content needs and the content overflows its own box sideways, landing on top of .agent-header-main instead of wrapping cleanly. Confirmed reproducible at 320px, not a one-off capture glitch, before settling on the flex-shrink-only fix. Verified 500px (the width mara flagged) and 1400px both clean, no overflow, no overlap. Below ~450px there's now a real mathematical floor — icon + main's shortest-unbreakable-word + pills' widest-single- badge together exceed the viewport — that's a genuine follow-up scope (icon-only badges or similar at that point), not something this fix claims to solve; flagging rather than silently leaving it implied. tsc n/a (CSS-only change), build clean, both pre-push lints clean. |
||
| .. | ||
| 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/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).