How yudswin/nettubefe works
Project type and purpose
• This is a single‐page frontend application (“NetTube Frontend”) built with React (v19), TypeScript, and Vite.
• Purpose: Provide a responsive UI for browsing, searching, authenticating, and playing video streams (HLS) via a backend API.
File structure
• Top level:
• index.html + public/ → Static assets and HTML shell.
• src/main.tsx → React app entry point.
• src/App.tsx → Root component, mounts Router & Context providers.
• src/routes/index.ts → Defines React Router route‐to‐page mappings.
• src/pages/… → Page components (e.g., home.tsx, browse.tsx, person.tsx, movie.tsx, plus nested /contents tabs).
• src/components/… → Reusable UI pieces organized by feature (create modals, feedback, forms, layout, search, ui cards/modals, user views).
• src/contexts/… → React Context providers (AuthContext, LanguageContext).
• src/services/… → API service layer using Axios (auth, content, streaming, user, genre, etc.).
– services/http/client.ts sets up Axios instance & interceptors.
– services/junction holds many‐to‐many endpoints.
• src/types/… → TypeScript defs for API requests/responses.
• src/utils, src/libs → Utility functions (e.g., jwtUtils) and helpers.
• Configuration: vite.config.ts, tsconfig*.json, tailwind.config.js, eslint.config.js.
Extract architecture insights from README
• Component‐based UI
• React Router for navigation
• Context API for global state (Auth, Language, Player)
• Axios + interceptors for RESTful API calls
• HLS.js for adaptive video playback
• TailwindCSS + DaisyUI for styling
• Vite for build & dev server
• Deployment targets: static hosts or Docker/Nginx
a. Main Components
• Browser / Client
• Static Host / CDN (serves index.html + JS/CSS bundle)
• React SPA
• Routing Layer (React Router)
• UI Presentation Layer (Components & Pages)
• State Management Layer (Context Providers)
• Service Layer (Axios HTTP client & service modules)
• External Services
• Backend API (user, auth, content, media metadata)
• Media Server (HLS segments)
b. Relationships & Data Flow
1. User interacts with UI → triggers React component events.
2. Components call service methods → Axios client attaches JWT header via interceptor.
3. Axios sends HTTP requests → Backend API (VITE_API_URL).
4. API returns JSON → Service layer normalizes → updates Context or local component state.
5. For video playback, HLS.js in <video> tag fetches media segments directly from Media Server (VITE_MEDIA_URL).
6. Context Providers wrap App: provide auth state, language prefs, player state to component tree.
c. Architectural Patterns & Principles
• Separation of concerns:
• Presentation (components/pages) vs. Data fetching (services) vs. State (contexts)
• Container/Presentational split within components (e.g., cards vs. model modals)
• Dependency Injection via Context
• Single Responsibility: each service module handles one entity
d. Key Technologies
• React + TS + Vite
• React Router
• TailwindCSS + DaisyUI
• Axios + interceptors
• HLS.js
• Context API
Detailed Capture of Architectural Elements
• Inter‐context connections (AuthContext → Axios interceptor).
• Environment variables (VITE_API_URL, VITE_MEDIA_URL).
• Where HLS.js is initialized (MediaCard or Player page).
• Build pipeline (Vite dev server vs. production build).