developervelnix-lab/winco_frontend

Purpose and Runtime

This is a Vite-built React single-page client for an online casino/betting experience. It provides public game discovery, authentication, game launch UI, wallet-related journeys, account management, betting statements, promotions, and responsible-gambling/legal content. The README contains no operational documentation.

Core browser entry points are index.html, src/main.jsx, and src/App.jsx. Build/runtime configuration is in vite.config.js; a generated service-worker distribution exists under dev-dist/.

Application Shell and Navigation

src/App.jsx is the likely composition and route boundary for the SPA, with global styles in src/App.css and src/index.css. Navigation and persistent account controls are assembled from:

• src/components/navbar/Navbar.jsx

• src/components/navbar/BelowNavbarComponent.jsx

• src/components/navbar/MobileFooterNav.jsx

Desktop/mobile navigation directs users between lobby, account, transaction, promotion, and policy flows. Page implementations are primarily grouped under src/components/pages/, while duplicate top-level pages/ files appear to be an alternate or legacy page location.

Global State, Theme, and Access Control

Application-wide state is separated into focused React contexts:

• src/context/SiteContext.jsx

• src/context/GameContext.jsx

• src/context/ThemeContext.jsx

GameContext is the likely handoff layer between game selection and launch/display components. Theme state and token synchronization are centralized in src/constants/ThemeSynchronizer.jsx and src/constants/theme.js, with consumers supported by src/hooks/useColors.js.

Authentication screens and route gating are contained in:

• src/components/auth/Login.jsx

• src/components/auth/Register.jsx

• src/components/auth/ProtectedRoute.jsx

This establishes a public-versus-authenticated boundary around account and monetary features.

Casino Lobby and Game Discovery

The home/lobby is componentized into content rails and verticals rather than a single monolith:

• src/components/home/Home.jsx

• src/components/home/CasinoLobby.jsx

• src/components/home/GameSection.jsx

Game catalog content appears locally data-driven through modules in src/components/jsondata/, including slotgames.js, live.js, sport.js, turbogames.js, and gameproviders.js. UI stages filter/select providers and games, render category sections, and pass selected games to launch/play surfaces such as src/components/common/GameLaunchModal.jsx and src/components/GamePlayComponent.jsx.

Account, Wallet, and Betting Operations

Authenticated customer journeys are represented as page-level screens:

• src/components/pages/DepositPage.jsx

• src/components/pages/WithdrawPage.jsx

• src/components/pages/Transaction.jsx

Account administration is centered on src/components/pages/AccountSetting.jsx and src/components/pages/ChangePasswordPage.jsx. Betting/history functionality is split between src/components/pages/OpenBetPage.jsx, src/components/pages/ProfitLossPage.jsx, and statement components in src/components/sidebar-components/statements/. These flows are UI boundaries for financial transactions and betting records; backend contracts are not present in the tree.

API, PWA, and Deployment Boundary

src/utils/apiFetch.js is the central visible API-access abstraction and should be the primary boundary for adding auth headers, error normalization, or backend integration. No server implementation is included; read_address.php is the only PHP artifact and is outside the React source structure.

PWA installation behavior is exposed through src/hooks/usePWAInstall.js and src/components/home/AppInstallHero.jsx. Service worker artifacts are checked in at dev-dist/registerSW.js, dev-dist/sw.js, and dev-dist/workbox-5a5d9309.js. Static deployment assets and Apache configuration live in public/, including public/.htaccess.