How electrium-mobility/electriumap works
Project type and purpose
• From the root files (frontend/ and backend/ folders) and the README, this is a full-stack web mapping application (“The Map of the Future”).
• Frontend is built with Next.js (React, TypeScript), integrating MapBox and Firebase.
• Backend is a lightweight upload handler (JavaScript) plus a static page.
File structure
• Top-level:
• frontend/ – a Next.js app (package.json, tsconfig.json, src/app, public/images).
• backend/ – a standalone static page (index.html, styles.css) plus upload-handler.js.
• README files and repo config (.gitignore, CODEOWNERS, license, etc.).
• frontend/src/app: follows Next.js App Router conventions, with subfolders for pages:
• create-account, login, API routes (api/outlets → route.ts).
• Components folder contains MapBox.tsx, Overlay.tsx, heatmap.tsx, plus static pins.json.
• firebase folder for Firebase client init.
• backend/upload-handler.js suggests a micro-service (e.g., an AWS Lambda/Netlify Function) that processes file uploads.
README for additional insights
• No database folder in backend → likely uses static JSON (pins.json) or relies on Firebase for persistence.
Elements
• Labels for each component (e.g., “Next.js Frontend,” “Serverless Upload Function,” “Firebase Auth,” “MapBox API”).
• Browser → CDN/Next.js
• Next.js → Firebase Auth
• Next.js → /api/outlets → Data Store
• Browser → MapBox
• Browser → upload-handler → Cloud Storage