press_sprint/
├── frontend/ # React + Vite frontend application
│ ├── src/ # Source code
│ └── ... # Configuration files
└── server/ # Node.js backend application
├── src/ # Source code
└── ... # Configuration files
- React 18
- TypeScript
- Vite
- TailwindCSS
- Socket.IO Client
- Node.js
- TypeScript
- Express
- Socket.IO
Challenge: Players were unable to start the game after being ready in the lobby. The game state wasn't properly transitioning from the lobby to the gameplay screen. Solution:
- Identified that the socket connection and game state weren't being properly transferred between GameLobby.tsx and GamePlay.tsx components
- Leveraged previous Socket.IO experience to implement proper state management
- Ensured socket connection persistence across component transitions
- Node.js (v18 or higher)
- npm or yarn
cd frontend
npm install
npm run devcd server
npm install
npm run dev-
Architecture
- Separated frontend and backend concerns
- Used component-based architecture for frontend
- Implemented RESTful API design for backend
-
Type Safety
- Implemented TypeScript throughout the project
- Used proper type definitions and interfaces
- Enabled strict type checking