Measured with Playwright (rAF frame deltas around a preset click, real Chromium, production): even with every CSS transition disabled, a single frame still spiked to ~133ms on preset switch -- proving the worst offender wasn't CSS at all, but the synchronous React re-render (reset() swaps the whole draft, re-rendering every ColorField/ GradientField and the ClickGui panel at once). Wrapped the three call sites that replace the whole draft (preset pick, reset-to-default, file import) in startTransition so React can deprioritize that render instead of blocking the frame the click lands on. Result (same measurement, after fix): peak frame 133ms -> 83ms, frames over 100ms: 1 -> 0. Not a full fix -- frames over 16ms actually rose slightly (18 -> 21), so total render cost is roughly the same, just spread out instead of landing in one blocking spike. A real fix for the remaining cost needs memoizing ColorField/GradientField so a preset switch doesn't re-render every field instance; noted as a follow-up, not done here. panel.test.tsx: import's name-box assertion now waits instead of checking synchronously, since the state update is deferred. Claude-Session: https://claude.ai/code/session_01F1M1Jic1wTSn4igUENynmZ |
||
|---|---|---|
| .. | ||
| public | ||
| scripts | ||
| src | ||
| .env.example | ||
| .gitignore | ||
| .oxlintrc.json | ||
| ARCHITECTURE.md | ||
| bun.lock | ||
| index.html | ||
| package.json | ||
| PLAN.md | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| tsconfig.test.json | ||
| vite.config.ts | ||
LoVisual Website
The frontend for LoVisual - a marketing site with a live in-game GUI demo, download page, documentation, themes/showcase pages, and an account dashboard with a cloud config manager. UI is fully bilingual (Russian default, English toggle, persisted in the URL).
Stack
- React 19 + TypeScript + Vite, package manager: bun
- Tailwind CSS v4 with custom design tokens (radii, glass panels, control sizing)
- TanStack Query for backend calls, react-router for pages
- react-i18next -
ru/enresources per feature, compile-time key parity viasatisfies - motion/react for animation, vitest + Testing Library for tests
- oxlint for linting
Layout
src/
├── app/ router, providers, App shell
├── features/ one folder per domain (account, cloud, demo, themes, ...)
│ └── <f>/ api.ts · i18n/{ru,en}.ts · components/ · tests/
├── pages/ route-level pages composing features
├── shared/ ui primitives, i18n bootstrap, easter eggs, helpers
└── test/ vitest setup and utilities
Feature-folder rules: API calls, translations and components live together; no cross-feature
imports except through shared/.
Scripts
bun install # install dependencies
bun run dev # dev server on http://localhost:5173 (proxies /api to the backend)
bun run test # vitest run
bun run build # tsc -b + vite build → dist/
bun run lint # oxlint
bun run gen:themes # regenerate theme tokens from the mod palette (scripts/extract-themes.ts)
The dev server expects the Rust gateway on 127.0.0.1:8080 (see backend/);
without it, API-backed pages degrade to demo/offline states by design.
Testing
Unit and component tests are colocated in features/*/tests/ and shared/**/tests/;
run a single file with bunx vitest run src/features/account/tests/account.test.tsx.
Translation parity (ru ↔ en key sets) is enforced at compile time and in tests.