How nishit-luhadia30/internship-techhyaku works
Project type and purpose
• This is a front-end single-page application (SPA) built with React and Vite.
• There is no custom backend in this repo—everything runs in the browser or in the dev/build pipeline.
File structure
• Top-level files:
– package.json / package-lock.json: Node.js dependencies and scripts
– vite.config.js: Vite bundler configuration
– eslint.config.js: Linting rules
– index.html: SPA entry point
• public/: static assets that are copied as-is into the final build
• src/: application source
– main.jsx: application bootstrap (Vite injects HMR code here)
– App.jsx: root React component
– components/: React component modules for each page/section
– assets/: images or other media organized by section
• Build & serve scripts triggered via npm/yarn in package.json
Readme insights
• Describes usage of @vitejs/plugin-react or plugin-react-swc for Fast Refresh
• Mentions ESLint and a hint toward possibly adopting TypeScript
Main components
A. Developer Workstation
• Node.js + npm/yarn
• Source code in src/ + public/ + config files
• ESLint
B. Build & Dev Pipeline (Vite)
• Vite Dev Server
• React plugin (Babel or SWC) for HMR
• Module resolution (ESM imports of .jsx, .css, .png, etc.)
• Dev → Browser (Live HMR over WebSocket)
• Vite Build → Static assets (bundled JS/CSS under dist/)
C. Deployment / Hosting
• Static hosting service (Netlify, Vercel, S3 + CloudFront, etc.)
• CDN delivering built assets
D. Runtime in Browser
• index.html
• React app bundle
• React Router (if used) loads components: Header, Footer, Home, About, Courses, etc.
• Assets loaded via import or public/ fallback
Relationships & data flow
• Code edits → (npm run dev) → Vite Dev Server transforms & serves → Browser HMR updates
• Code ready for production → (npm run build) → Vite bundles → dist/ → Deploy to static host → Browser fetches built JS/CSS → React hydrates UI
• Components import from src/assets or src/components → Vite inlines or copies static assets
Architectural patterns & design principles
• Component-based UI (React)
• SPA pattern with client-side routing (if applicable)
• Development vs. production pipelines separated by Vite config
• Static asset management in public/ and via import