How kshat111/snow-shield-aware works
Project type and purpose
• This is a single-page front-end application built with Vite, React, and TypeScript.
• It uses shadcn-ui (a component library built on Radix + Tailwind CSS) for UI, Tailwind for styling, and Firebase (via firebase.js at the root) for authentication (and likely database).
• The app has multiple “pages” (Dashboard, Map, Reports, etc.) and uses React Router (implicitly via App.tsx or main.tsx) to switch views.
File structure
• Top-level files:
• index.html – SPA entry point
• firebase.js – Firebase initialization
• bun.lockb, package.json / lock, tsconfig, vite.config.ts – build & config
• Key directories under src:
• main.tsx – React app bootstrap
• App.tsx + App.css – root component & styling
• layouts/ – AppLayout.tsx (site shell: nav, sidebar)
• pages/ – each route’s view (Dashboard, Login, Map, etc.)
• components/ – domain-specific components (Logo, WeatherCard, SOSButton, ReportCard, RiskBadge)
• components/ui/ – UI primitives (accordion, button, dialog, etc.) provided by shadcn-ui
• context/ & src/context – AuthContext (provides user state & auth methods)
• hooks/ – custom React hooks (use-mobile, use-toast)
• lib/ – utilities (utils.ts)
• public/assets – static files (robots.txt, other public assets)
Additional insights from README
• Standard dev flow: npm i, npm run dev under Vite
• No server-side code here—relies on Firebase or third-party APIs for data/storage
• Tech stack reiterated: Vite, TypeScript, React, shadcn-ui, Tailwind CSS