How amansatya/pulse-roadway-insight works
Project type and purpose
• This is a single-page, client-side React application scaffolded with Vite, written in TypeScript.
• It consumes data (real-time or batch) for traffic system visualization and control (e.g., JunctionHeatmap, TrafficLight3D, EmergencyAlert, PerformanceChart).
• The repository contains no backend code, so we assume APIs or WebSocket endpoints are provided by an external service (e.g., your traffic-control backend or Lovable’s runtime).
File structure
• Top-level files: package.json (dependencies & scripts), vite.config.ts (build & dev server), tailwind.config.ts, tsconfig.json.
• public/: static assets (robots.txt, index.html template).
• src/
• main.tsx: application entry point (mounts React tree)
• index.css + Tailwind styling
• lib/utils.ts: shared utilities (formatting, API clients)
• hooks/: custom React hooks (use-toast, use-mobile)
• pages/: routing targets (Index.tsx = dashboard; NotFound.tsx)
• components/: feature components (ApproachLane, JunctionControl, VideoPlayer, etc.)
• components/ui/: primitive UI building blocks provided by shadcn-ui (buttons, dialogs, form controls, etc.)
README for additional insights
• Lists tech stack: Vite, React, TypeScript, Tailwind CSS, shadcn-ui.
• Deployment and editing flow are all managed by the Lovable platform, which provides live preview, commits, and publishing to static hosting or custom domains.
Key reminder
• Be exhaustive but not overly granular: capture every major subsystem (Build → Host → Runtime → API) and all internal layering (Pages → Features → UI Primitives).
• Critical configuration (e.g., Tailwind config, Vite plugins).