TehRiehlDeal
31e2600f60
Versus, Game Night and Async Versus could never complete a match. startGameFromVersus was a copy of startGame minus the session-creation block, so sessionId stayed null. score is only ever assigned inside the `if (sessionId)` branch of the completion handler, and every multiplayer submission is gated on score being non-null - so the submit never fired, the opponent was never told, and the match never resolved. The completion modals had no dismiss path, making it an unrecoverable dead end. - startGameFromVersus now creates the session and reports the outcome as 'started' | 'superseded' | 'failed'. The middle case matters: React StrictMode remounts the effect and its cleanup resets the store, which must not be reported to the player as an error. - Completion moves into finalizeGame, which awaits an in-flight session rather than racing it (a fast player could close the loop first) and always resolves to a score or a visible error, never a silent null. - A generation counter retires work belonging to abandoned games, so a slow session-creation response can no longer attach itself to the next game. - Achievements are no longer stored on `score`. They were posted back to the API, where forbidNonWhitelisted rejected the submission with a 400. - A failed async submit is no longer retried on every render; it previously fired ~20 identical failing requests. - The versus and game-night completion modals gained a way out so a stalled opponent is not a trap. Verified end to end: an async match played to completion submits, and Postgres records the score against both the match and the session.
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])