| Filename | Latest commit message | Latest commit date |
|---|---|---|
colors.css shipped one fixed dark (Catppuccin Mocha) palette with no light variant and no OS/browser-preference detection, so anyone without a stylix-managed session (a phone browser, a future PWA install) got the dark palette regardless of their light-mode preference. This is an accessibility gap, not a cosmetic one - some people need light for low-vision/contrast reasons, others need dark for photosensitivity, the same reasoning that already gates prefers-reduced-motion elsewhere. Add a Catppuccin Latte row behind `@media (prefers-color-scheme: light)`, ported through the identical base16 slot mapping (including the existing sky-over-teal base0C substitution) so a swap between the two rows never changes what a slot means. A stylix-generated colors.css replaces the file wholesale with a single unconditional :root block and has no media query in it, so a themed deployment is unaffected either way. Verified with headless chromium screenshots forcing both prefers-color-scheme values against the built swarm-ui bundle - both render with correct contrast, and the default (no forced preference) render matches the light row. |
||
| .. | ||
| 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).