How surajbkale/chessverse works
ChessVerse is a real-time multiplayer chess platform. A player enters through the web app, authenticates or plays as a guest, starts random matchmaking or joins a shared game, then plays and reviews moves over WebSockets. The backend handles login and sessions; the WebSocket service coordinates matching, game state, persistence, and reconnectable room delivery. The README also documents profile/statistics, themes, board controls, sharing, and game-result features. Some feature components are unsampled, so their placement follows documented capabilities; edges are limited to visible calls or README statements.
Main entry points: Game.tsx Game screen · App.tsx App routes · index.ts API server · GameManager.ts Match and room manager
Components 20
Web client
- App routes
apps/frontend/src/App.tsx - Landing and match
apps/frontend/src/screens/Landing.tsx - Login screen
apps/frontend/src/screens/Login.tsx - Game screen
apps/frontend/src/screens/Game.tsx - Chess board
apps/frontend/src/components/ChessBoard.tsx - Move history
apps/frontend/src/components/MovesTable.tsx - Themes
apps/frontend/src/components/themes.tsx - Socket connection
apps/frontend/src/hooks/useSocket.ts
Identity and API
- API server
apps/backend/src/index.ts - Auth routes
apps/backend/src/router/auth.ts - OAuth strategies
apps/backend/src/passport.ts - V1 API routes
apps/backend/src/router/v1.ts
Realtime gameplay
- Match and room manager
apps/ws/src/GameManager.ts - Game state
apps/ws/src/Game.ts - Socket rooms
apps/ws/src/SocketManager.ts - Redis
Shared state
- PostgreSQL
- Shared game and user state
packages/store/src/atoms/user.ts
Other components
- Player
- Google / GitHub
Connections 30
- Player → App routes: uses
README.md - App routes → Landing and match: routes to
apps/frontend/src/App.tsx - App routes → Login screen: routes to
apps/frontend/src/App.tsx - App routes → Game screen: routes to
apps/frontend/src/App.tsx - App routes → Themes: routes to
apps/frontend/src/App.tsx - Player → Login screen: authenticates
README.md - Login screen → API server: requests auth
- Google / GitHub → Auth routes: authenticates
README.md - API server → Auth routes: mounts
apps/backend/src/index.ts - API server → OAuth strategies: initializes
apps/backend/src/index.ts - API server → V1 API routes: mounts
apps/backend/src/index.ts - Auth routes → PostgreSQL: reads and writes users
apps/backend/src/router/auth.ts - Auth routes → OAuth strategies: authenticates with
apps/backend/src/router/auth.ts - Landing and match → Game screen: starts play
README.md - Game screen → Socket connection: opens connection
apps/frontend/src/screens/Game.tsx - Socket connection → Shared game and user state: reads user token
apps/frontend/src/hooks/useSocket.ts - Socket connection → Match and room manager: sends game messages
- Game screen → Chess board: renders
apps/frontend/src/screens/Game.tsx - Game screen → Move history: renders
apps/frontend/src/screens/Game.tsx - Chess board → Shared game and user state: uses board state
apps/frontend/src/components/ChessBoard.tsx - Chess board → Player: accepts moves
README.md - Match and room manager → Game state: creates and dispatches
apps/ws/src/GameManager.ts - Match and room manager → PostgreSQL: loads games
apps/ws/src/GameManager.ts - Match and room manager → Redis: claims pending match
apps/ws/src/GameManager.ts - Game state → PostgreSQL: persists moves and results
apps/ws/src/Game.ts - Game state → Socket rooms: broadcasts results
apps/ws/src/Game.ts - Socket rooms → Redis: publishes and subscribes
apps/ws/src/SocketManager.ts - Socket rooms → Player: delivers room updates
apps/ws/src/SocketManager.ts - Game state → Player: runs timed chess
README.md - Player → Game screen: reviews moves
README.md