| Filename | Latest commit message | Latest commit date |
|---|---|---|
Fixes a real bug argus caught: the flat batch-round topo sort could interleave two fully independent dep pairs in the same sibling list (e.g. W, X after_ok(W), Y, Z after_ok(Y) reordered to W, Y, X, Z), and the single-column rail then drew one continuous line across rows that have no relationship at all. Reorder is now scoped per connected component of the local dependency graph -- each component renders as a contiguous block (first-seen order, so an already-correct list doesn't reorder needlessly), so two unrelated pairs can never weave together. Within one component, overlapping ranges are still correct: they mean the nodes really are related (a diamond, for instance). Also: a pass-through row's tooltip now names what's passing through it (not just the edge it's itself an endpoint of) -- addresses the same disambiguation gap argus flagged as a secondary note. Re-verified against a wider fixture set including the exact interleaving case from the review (17 checks: prior 6 unaffected + argus's regression case, a shuffled-order variant, three simultaneous independent pairs, and a genuine diamond that's expected to overlap). |
||
| .. | ||
| 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).