How gauravkesh/expense-tracker works
Project type and purpose
• This is a modern, full-stack Personal Finance Tracker.
• Frontend: Next.js (App Router + legacy pages), React, TypeScript, Tailwind CSS and shadcn/ui.
• Backend: Separate Node.js REST API (hosted on Render).
• Database: MongoDB (likely Atlas).
• Purpose: allow users to create and manage transactions, budgets, categories, and view analytics via charts.
File structure
• Top-level Next.js app directory:
– /app: App Router pages (dashboard, settings, transactions)
– /pages: legacy page-based routing for BudgetsPage, CategoriesPage, etc.
– /components: atomic and composite UI (cards, charts, forms, layout, modules, and shadcn/ui primitives)
– /lib: utility functions and API‐endpoint helpers (piendpoint.ts)
– Configuration: next.config.js, postcss.config.js, tailwind.config.ts, tsconfig.json, .eslintrc.json
• No local “api” folder—frontend calls out to the separate Node.js API on Render.
• The presence of modular UI components (forms, charts, modals) indicates a clear component-driven architecture.
README for additional insights
• Confirms tech stack, features, API endpoints (transactions, budgets, categories).
• Backend API URL: https://personal-expense-backend.onrender.com/api/....
• Emphasis on charts (Recharts), state management via React hooks, shadcn/dialogs for modals.
Essential architectural elements
• Separation of concerns: UI vs. business logic vs. data layer.
• CRUD flows for transactions, budgets, categories.
• Where styling (Tailwind), charts (Recharts), dialogs (Radix) fit into the frontend.
• Do not over-complicate—focus on the core components and their interactions.