| Filename | Latest commit message | Latest commit date |
|---|---|---|
hive-c0re's broker reminder store and /api/reminders endpoint were removed in PR #2644 (reminders migrated to in-container sqlite store). The dashboard had a QU3U3D R3M1ND3RS section on the schedules tab backed by that endpoint, and a per-agent badge driven by pending_reminders (always 0 after the migration). Remove both. Per-agent reminders now surface through get_loose_ends / the todos pill on the agent page, consistent with the todos migration. - frontend/packages/dashboard/src/schedules.js: drop refreshReminders, renderReminders, applyRemindersChanged; drop appendLinkified import (no longer used); update module comment. - frontend/packages/dashboard/src/tabs.js: drop applyRemindersChanged and refreshReminders imports; remove reminders-section from managed list; remove refreshReminders call site; drop reminders_changed from SSE dispatch; simplify countdown ticker (reminder-due gone). - frontend/packages/dashboard/src/dashboard.html: remove QU3U3D R3M1ND3RS section. - frontend/packages/dashboard/src/dashboard.css: remove reminder list + row CSS. - frontend/packages/dashboard/src/common.css: remove .badge-reminder. - frontend/packages/dashboard/src/swarm.js: remove pending_reminders from fingerprint key and badge render. |
||
| .. | ||
| 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).