| Filename | Latest commit message | Latest commit date |
|---|---|---|
Pre-step-2, the SSE subscription on /index.html was conditionally created by the broker-terminal IIFE that only ran on /flow.html (via the `if (!flow || !window.HiveTerminal) return;` guard) — so the dashboard only updated on cold load + after async-form submits. The split in step 2 made the gap more obvious; close it. Bare `EventSource` (the dashboard doesn't render broker rows, so none of the HiveTerminal infrastructure is wanted here). Each event's `kind` looks up against a `MUTATION_HANDLERS` table that fans out to the existing `applyXxx` handlers. Unknown kinds (broker `sent` / `delivered`, anything the backend adds later) silently no-op. On (re)connect we kick `refreshState()` to recover events lost during the disconnect window — same pattern as flow.js's `onStreamOpen`. EventSource handles auto-reconnect. #408 will give /index.html its own stream that omits broker traffic; for now both pages subscribe to `/dashboard/stream` and filter client-side. Closes the #406 architectural roadmap: - step 1 (#410): common.js extraction ✓ - step 2 (#412): split into app.js + flow.js entry points ✓ - step 3 (this PR): /index.html re-acquires its SSE subscription |
||
| .. | ||
| 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).