marvinandClaude Opus 5.5
87151c2cc9
The round summary used to disappear after a fixed 5 seconds. It is now derived from the game state: the previous round's result is shown while the new round is in bidding and hides once card play starts. This also survives a page reload. - Drop the client-side round timer from useWizard - On narrow screens show the summary in the page flow so it does not cover the bid buttons Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wizard_website
React + TypeScript frontend (Vite). All component styles are CSS modules
(*.module.css); the design tokens live on the .app root in
src/App.module.css.
npm install
npm run dev # http://localhost:5173, proxies /api/* (incl. websocket) to localhost:8000 without the /api prefix
npm run build
npm run lint
The app is built with relative asset paths and connects to ../api/ws relative to its own URL
(/wizard/website/ → /wizard/api/ws). Set WIZARD_SERVER_URL to proxy to another server in
development, or VITE_WS_URL at build time to use an absolute websocket URL instead.
Structure
src/api/— protocol types and theuseWizardhook (websocket connection, reconnect with a per-tab session token, game state)src/components/— reusable UI (button, playing card, modal, toasts)src/screens/HomeScreen— enter a name, create or join a lobbysrc/screens/LobbyScreen— lobby code, players, AI players, rule options, startsrc/screens/GameScreen— the table: seats, trick, hand, bidding, trump choice, scoreboard, round summary, game over