Admin
8d178884d4
Sidebar, Queue, PlayerBar, TabsBar, and the hero/spotlight surfaces all had an extra CSS `transition: background 0.5s ease-out` (theme-transition/ glass-bar) layered on top of backgrounds that are already animated frame-by-frame over 600ms by the hue-interpolation loop in +layout.svelte. That extra transition made them visibly lag behind and take a different amount of time than the main app-backdrop, which has no such transition and therefore tracks the JS animation exactly. Drop the redundant transition so every hue-driven surface updates in lockstep. Also fixes a dangling --color-btn-hover: var(--mf-btn-bg-hover) that referenced an undefined custom property (theme.css never defined --mf-btn-bg-hover after an earlier partial commit), which silently broke the secondary button's hover background.
web-player
Musify's web client: SvelteKit 2 (adapter-node), Svelte 5 runes, Tailwind 4,
TypeScript. Authentication is server-side OIDC against Zitadel (openid-client
and jose) with an encrypted session cookie; the backend is called from load
functions and form actions through a typed openapi-fetch client.
Development
npm install
npm run dev # :5173
Configuration lives in .env (template in .env.example). Bring the
infrastructure stack up first (see ../deploy/README.md)
and copy the WEB_CLIENT_ID / WEB_CLIENT_SECRET it writes to deploy/.env
into this .env once, then run the dev server.
npm run check # svelte-check — must be clean before closing a change
npm run lint # prettier --check . && eslint .
npm run format # prettier --write .
npm run build # production build into build/
npm run gen:api # regenerate src/lib/api/schema.d.ts from the running API
Production
Built and run as a container by the production stack — see
../deploy/README.md. There the same variables come from
deploy/.env.prod through compose instead of from .env.
Conventions and the design system are documented in CLAUDE.md and
in the musify-web skill.