How adityakumarsingh8077/portfolio_adityakumarsingh works
Project type and purpose
• This is a front-end single-page application built with React and Vite.
• There is no backend or database in this repo; its sole role is to bundle, serve, and hot-reload a React UI.
File structure
• Top-level: package.json (dependencies, scripts), vite.config.js (build/dev server config), index.html (app shell).
• src/: the React application code.
• main.jsx: ReactDOM.render entry point.
• App.jsx: root component.
• components/: leaf and container components organized by feature (about, contact, hero, navbar, parallax, portfolio, services, sidebar).
• SCSS modules alongside each component.
• public/: static assets (if any).
• ESLint config at the root.
README
• Confirms minimal React + Vite setup with HMR and ESLint.
• No higher-level architecture guidance is provided in the README.
a. Main components
• Developer Machine (Node.js, npm/yarn)
• Vite Dev Server (HMR, ES modules)
• React Application Code (src/, App.jsx, components/)
• Static Assets (public/)
• Browser (runs bundled JS/CSS)
• Production Host/CDN (serves built static files)
b. Relationships & data flow
1. Developer writes code in src/ & public/.
2. npm run dev → Vite reads index.html & src/main.jsx → compiles modules on the fly.
3. Vite’s dev server pushes updates via HMR to the Browser.
4. Browser renders React tree: App → various feature components.
5. For production: npm run build → Vite bundles JS/CSS → output to dist/ → deploy to static host/CDN → Browser fetches static files.
c. Architectural patterns / design principles
• SPA: single HTML shell (index.html).
• Component-based design: reusable, feature-scoped React components + SCSS modules.
• HMR for rapid feedback loops.
• Module federation is not used; it’s a monolithic front-end.
d. Key technologies
• React (UI library)
• Vite (dev server & bundler)
• Node.js/npm (build tooling)
• SCSS (style modules)
• ESLint (code quality)