| Filename | Latest commit message | Latest commit date |
|---|---|---|
7d1b18d2c8
Project-bootstrap scope per the issue: static build as a nix pkg, empty start page for now, functionality deferred until auth against authelia is figured out. Stack (Preact + wouter + TypeScript + JSX) matches the shell decision from the earlier framework-paths thread — a real SPA shell with a router and deep links, distinct from the per-hive dashboard's vanilla-JS + custom-element MPA. - New npm workspace frontend/packages/swarm-ui: one route (/), a wouter Switch/Route shell, a 404 fallback. Reuses @hive/shared's colors.css/theme.css/base.css for visual consistency; no other shared JS (the vanilla-JS el()/dom.js helpers are superseded by Preact in this shell). - nix/packages/swarm-ui.nix: its own buildNpmPackage derivation (scoped to just this workspace via an explicit buildPhase), not folded into nix/packages/frontend.nix's packages.default closure — same reasoning swarm-controller/swarmctl already use for staying out of daemonBins: a hive that doesn't run the swarm controller shouldn't carry swarm-ui bytes. - npmDepsHash recomputed in both frontend.nix and swarm-ui.nix (same shared lockfile, new deps: preact, wouter-preact, typescript). - Added swarm-ui to nix/checks.nix alongside frontend, for the same FOD-staleness reason plus being the only thing that actually builds it in CI (not in packages.default's closure like frontend is, so nix flake check wouldn't otherwise touch it). - npm run typecheck (tsc --noEmit) is available locally; not yet wired into CI — esbuild transpiles TS without type-checking, so that's a real gap, left as a follow-up rather than growing this bootstrap PR with a new CI workflow step. Verified: nix build .#swarm-ui and .#frontend both succeed; npm run build (root, all workspaces) succeeds; tsc --noEmit clean; scripts/check-issue-refs.sh clean. |
||
| .. | ||
| 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).