How aurorateam/auroralauncher works
Main Components Identification
The system consists of five main packages:
• API Package (Client-Server Communication)
• Core Package (Shared Code)
• ESBuild Decorators (Build Tool Plugin)
• Launcher (Client Application)
• Server (Backend Service)
Client Layer
• ↓
API Layer
• ↓
Server Layer
• ↓
Core Services Layer
Component Relationships
• Launcher ←→ API (WebSocket & HTTP communication)
• API ←→ Server (Request handling)
• Server → Core (Utility functions)
• Server Components (Internal connections):
• WebServer ←→ Auth Manager
• WebSocket ←→ Clients Manager
• Auth Manager ←→ Profile Manager
• Download Manager ←→ Update Manager
Specific Implementation Details
• Blue rectangles: Core components
• Green hexagons: API endpoints
• Yellow diamonds: Managers
• Red circles: Authentication components
• Purple rectangles: External services
Important Subsystems to Highlight
Authentication System:
• Multiple auth providers (Accept, Database, JSON, etc.)
• Session management
• Profile handling
API Layer:
• WebServer endpoints
• WebSocket connections
• Request/Response handling
Download System:
• Multiple download managers (Fabric, Mojang, Quilt)
• Update management
• Profile synchronization
Technical Details
Annotations for:
• TypeScript usage throughout the project
• ESBuild integration
• Configuration file formats
• Storage mechanisms
• Authentication flows