How avigupta309/e-bazzar works
Project type and purpose
• This is a single-page application (SPA) built with React and Vite.
• Purpose: A front-end “E-Bazzar” / “Attaindance” shopping interface that manages products, routing, and a shopping cart via React Context.
File structure
• Top-level config:
• package.json / package-lock.json – dependencies and scripts (Vite, React, ESLint).
• vite.config.js – Vite build/dev configuration.
• vercel.json – static-hosting settings for deployment.
• eslint.config.js – linting rules.
• public directory & index.html – the static container for the built app.
• src directory – main application code:
• main.jsx – entry point, ReactDOM.render into root element.
• Router.jsx – defines client-side routes.
• Context/ContextApi.jsx – global state provider for cart data.
• Components: Header/Header.jsx, App.jsx, CartSection.jsx, Product.jsx.
• Assets (src/assets, CSS files).
• api.txt – likely documents external API endpoints the app consumes.
Key insights from the README
• Uses Vite’s React plugin (Babel or SWC) for hot-module reload.
• Minimal boilerplate focused on rapid front-end iteration.
• No built-in backend—expects to call an external REST API (documented in api.txt).
Detail and granularity
• Config files separately (vite.config.js, vercel.json) to illustrate deployment/build influences.
• “api.txt” as a documentation artifact pointing to external API specs.