| Filename | Latest commit message | Latest commit date |
|---|---|---|
Part of #3591 (mara: "pop ups and menus appearing should animate"). Each popover mounts fresh on open ({open ? <div> : null}, not a state transition), so a keyframe animation on the popover element itself is the right tool -- same shape as Shell.css's own shell-page-enter (fade + a slight translate/scale settle), including the identical three-rule motion-guard (base rule, prefers-reduced-motion media query, data-motion=reduce/allow explicit overrides). Scope: LinksMenu, SettingsMenu, UserMenu -- the three header popovers. Not included here (posted findings on the issue instead of guessing): the refresh-interval picker's dropdown (native <select>, whose open popup is OS/browser chrome outside CSS reach in current browsers -- "not themed" is a platform limitation, not a bug in this component's own styling) and the jobs graph's node animations (JobqGraph is a @hive/shared component consumed by both swarm-ui and the per-hive dashboard, real design/implementation work on shared infra, not a same-shape mechanical extension of an existing pattern). Screenshot-verified the settled (post-animation) state renders correctly; a static screenshot cannot show an in-flight CSS animation, so this leans on exact structural parity with the already-shipped Shell.css pattern for the animation's own correctness. |
||
| .. | ||
| 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).