Service worker now applies the strategies the roadmap asks for :
* Static assets : StaleWhileRevalidate (already in place)
* HLS segments : CacheFirst, max-age 7d, max 50 entries
* API GET : NetworkFirst, 3s timeout
Stayed on the hand-rolled fetch handlers rather than migrating to
Workbox — the existing implementation already covers push notifications
+ background sync + notificationclick, and Workbox would bring 200+ KB
of runtime + a build-step dependency for a feature set we already have.
Changes
- public/sw.js
* HLS_CACHE_MAX_ENTRIES (50) + HLS_CACHE_MAX_AGE_MS (7d) +
NETWORK_FIRST_TIMEOUT_MS (3s) tunable at the top of the file.
* cacheAudio : reads the cached response's date header to skip
stale entries (>7d), and prunes the cache FIFO after every put
so the entry count never exceeds 50. Network-down path still
serves stale entries (the offline-playback acceptance).
* networkFirst : races the network against a 3s timer ; if the
timer fires AND a cached entry exists, serve cached + let the
network keep updating in the background. Timeout without a
cached fallback lets the network race continue.
* isAudioRequest now matches .ts and .m4s segments too (HLS).
- scripts/stamp-sw-version.mjs (new) : postbuild step that replaces
the literal __BUILD_VERSION__ placeholder in dist/sw.js with
YYYYMMDDHHMM-<short-sha>. Pre-Day 16 the placeholder shipped
literally — same string across every deploy meant browser caches
were never invalidated. Wired into npm run build + build:ci.
- tests/e2e/31-sw-offline-cache.spec.ts : 2 tests gated behind
E2E_SW_TESTS=1 (SW only registers in prod builds — dev server
skips registration via import.meta.env.DEV check). When enabled :
(1) registration + activation, (2) cached resource served while
context.setOffline(true).
Acceptance (Day 16) : strategies match spec ; offline playback works
once the user has played the segment once before going offline. The
e2e self-skips on dev unless E2E_SW_TESTS=1 is set against vite preview.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Closes Phase 3 of the v1.0.8 OpenAPI typegen migration. With the four
feature-service migrations (B2 dashboard, B3 profile, B4 playlist,
B5 track, B6 partial auth) landed, the four remaining importers of
the legacy typescript-axios output were all consuming pure model
types — easily portable to the equivalent orval-generated models
under src/services/generated/model/.
Type imports re-pointed (4 sites):
- src/types/index.ts — VezaBackendApiInternalModelsUser /
Track / TrackStatus / Playlist
- src/types/api.ts — same trio (Track / TrackStatus / User)
- src/features/auth/types/index.ts — TokenResponse +
ResendVerificationRequest
- src/features/tracks/types/track.ts — Track / TrackStatus
Same shapes, sourced from openapi.yaml — orval and the legacy
generator were emitting structurally-identical interfaces because
swaggo's spec is the common source. Verified by `npm run typecheck`
clean and 1187/1188 tests green (1 skipped is the long-standing
ResetPasswordPage flake).
Cleanup performed:
1. `git rm -rf apps/web/src/types/generated/` — 198 files / ~23k LOC
of auto-generated typescript-axios output gone.
2. `npm uninstall @openapitools/openapi-generator-cli` — drops the
~150 MB Java-bundled dependency tree from node_modules.
3. `apps/web/scripts/generate-types.sh` — collapsed from a two-step
"[1/2] legacy / [2/2] orval" pipeline to a single orval call.
4. `apps/web/scripts/check-types-sync.sh` — now diffs only
`src/services/generated/`. The "regenerate two trees" complexity
is gone.
5. `.husky/pre-commit` — message updated to point at the new tree.
Knock-on: the pre-commit hook should run noticeably faster (no Java
JVM spin-up to invoke openapi-generator-cli on every commit), and a
fresh `npm install` is leaner.
Not yet removed (still active under hand-written services):
- services/api/{auth,users,tracks,playlists,queue,search,social}.ts
— these wrap features/<feature>/api/* services and remain in use
by 2-15 callers each. They live in the orval-driven world (their
underlying calls go through orval mutator) and don't import the
legacy types, so they're safe parallel surfaces. Consolidation
punted to v1.0.9 once all auth/queue endpoints are annotated and
the remaining authService 5/9 functions ship.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Phase 1 of the OpenAPI typegen migration. Brings orval@8.8.1 into the
monorepo (workspace-hoisted) and wires a custom mutator so generated
calls route through the existing Axios instance — interceptors for
auth / CSRF / retry / offline-queue / logging keep firing unchanged.
200 .ts files generated from veza-backend-api/openapi.yaml (3441 LOC),
covering 13 tags (auth, track, user, playlist, marketplace, chat,
dashboard, webhook, validation, logging, audit, comment, users).
Changes:
- apps/web/orval.config.ts (NEW): generator config, output
src/services/generated/, tags-split mode, vezaMutator.
- apps/web/src/services/api/orval-mutator.ts (NEW): translates
orval's (url, RequestInit) convention into AxiosRequestConfig
then apiClient. Forwards AbortSignal for React Query cancellation.
- apps/web/scripts/generate-types.sh: runs BOTH generators during
the migration (legacy typescript-axios + orval). B9 drops step 1.
- apps/web/scripts/check-types-sync.sh: extended to check drift on
both output trees.
- apps/web/eslint.config.js: ignores src/services/generated/
(orval emits overloaded function declarations that trip no-redeclare).
- .gitignore: narrowed the bare `api` SELinux rule to `/api` plus
`/veza-backend-api/api`. The old rule silently ignored
apps/web/src/services/api/ new files including orval-mutator.ts.
- apps/web/package.json + package-lock.json: orval@^8.8.1 added
as devDependency, plus @commitlint/cli + @commitlint/config-conventional
(referenced by .husky/commit-msg but missing from deps).
Out of scope: no hand-written service changes. Pilot developer.ts
lands in B2, bulk migration in B3-B8, cleanup in B9.
npm run typecheck and npm run lint both green (0 errors).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- usePlaylistSearch: use useRef for toastError to avoid infinite loop in useEffect
- handlers-playlists: fix search response format (playlists/total/page/limit)
- handlers-playlists: fix list response (items -> playlists)
- handlers-playlists: add GET playlists/:id/analytics handler
- PlaylistSearch.stories: fix Empty story response format
- audit-storybook: add MSW, swagger, .mdx ignore patterns
- audit-storybook: cap errors per story (MAX_ERRORS_PER_STORY=100)
- Add playwright.config.storybook.ts: runs against storybook-static on :6007
- Add e2e/tests/storybook/storybook-all.spec.ts: one test per story (load iframe, no errors)
- Add scripts/serve-storybook-static.cjs: serves build or stub (empty index) when no build
- npm run test:storybook:playwright (after build-storybook) for full coverage
- Storybook decorator: use bg-background / design tokens for dark (#121212)
- Preview: default dark background #121212
- Button: secondary/ghost/glass aligned to Spotify/Discord (white/5, white/10 hover)
- KodoEmptyState: softer orbs, compact copy, primary CTA without heavy glow
Co-authored-by: Cursor <cursoragent@cursor.com>
