How ashutosh-live/charaka-fe-new works
Project Type and Purpose
• This is a single‐page front-end application built with React (TypeScript), Redux (Redux Toolkit slices), Webpack, and styled via SCSS/CSS.
• It’s packaged in Docker and served via Nginx. It “speaks” to one or more back-end APIs (authentication, product management, chats, OCR, etc.).
Top-Level Architectural Components
a. Container:
• Nginx (Docker container) – serves static assets and handles routing/fallback.
• React App – the compiled JS/CSS bundle.
b. Client-Side Modules:
• Pages (src/Pages) – route–based containers (Auth, Dashboard, Product, Plant, Additives, Chat, NotFound).
• Components (src/components) – reusable UI (Dialogs, Toaster, Chat modules, Swipers, Layout, Webcam, etc.).
• State Management (src/slices + src/store.ts) – Redux slices for auth, products, plants, additives, chat, dashboard, UI alerts/animations, etc.
• Services (src/services) – API abstractions per domain (auth.ts, product.ts, additives.ts, plants.ts, chat, OCR, etc.) built on a requestBuilder.
• Helpers & Utilities (src/helper, src/utils) – common functions (navigation, OCR handling, encryption, tag inputs, validation).
• Styling & Assets – SCSS partials (src/styles), CSS overrides (src/assets/css), images (src/assets/images).
Interactions & Data Flow
• User’s browser requests index.html → Nginx serves built React app.
• React Router directs to a Page component → Page mounts child Components.
• UI Components dispatch Redux actions → slices trigger async thunks which call Services.
• Services use requestBuilder → send HTTP/HTTPS requests to external backend APIs (Auth API, Product API, Plant API, Chat Server, OCR service).
• Responses update Redux store → UI re-renders.
• Real-time chat: potentially WebSocket or long-polling via Chat service.
Architectural Patterns & Principles
• Component Hierarchy: Page containers orchestrate child components; presentational vs. container separation.
• State centralization in Redux (single store, feature slices).
• API service layer abstracts HTTP details.
• SCSS modularity via partials (_components.scss, _index.scss).
• Build-time configuration: Webpack for dev/prod, Babel for TS/JX, ESLint/Prettier for code quality.
• Containerization best practices: Dockerfile for multi-stage builds, Nginx config for hosting.