How savire/ebuddy works
Project type and purpose
• This is a full-stack mono-repo managed by TurboRepo.
• It contains:
• a Next.js-based React frontend (/apps/frontend-repo)
• a Node/Express-style backend API with Firebase Cloud Functions support (/apps/backend-repo)
• a shared TypeScript package for common entities (/packages/shared)
• Its purpose is to showcase a simple “eBuddy” app using Firebase Auth & Firestore, running locally via the Firebase emulator.
File structure
• Top-level mono-repo:
• turbo.json – orchestrates parallel dev and emu scripts
• package.json – root scripts: turbo run dev / turbo run emu
• /packages/shared:
• entities/user.ts – shared domain model
• /apps/frontend-repo:
• Next.js “app router” under /app (layout.tsx, page.tsx, login/, member/)
• /apis/auth.js – client calls to Firebase Auth
• /store – Redux-style slice and store
• /components – UI dialogs, toasts, member action buttons
• /apps/backend-repo:
• config/firebaseAdmin.ts – initializes Firebase Admin SDK
• core/app.ts – configures Express app, middleware
• routes/userRoutes.ts + controller/api.ts – HTTP endpoints (REST)
• repository/userCollection.ts – data layer wrapping Firestore
• middleware/authMiddleware.ts – secures endpoints
• /functions – Firebase Cloud Functions definitions & emulator export data
README insights
• Dev commands:
• npm run dev – starts individual app
• npm run emu – starts Firebase emulator for functions
• turbo run dev|emu – runs both frontend & backend in parallel
• Emphasizes local Firebase emulation, requiring client auth config in /apps/frontend-repo/apis/auth.js
Detailed capture of architectural elements
• Don’t just show “frontend → backend.” Drill down to:
• Next.js App Router
• API layer in /apps/backend-repo/core/app.ts
• Middleware/auth
• Repository/firestore calls
• Cloud Functions folder for special tasks (data export)
• How the Firebase emulator suite connects to both functions and the Next.js client.