How longlekuro2106/finance-tracker-app works
Project Type and Purpose
• This is a full-stack finance tracker application (“finance-tracker-app”) consisting of:
• A React/Next.js 13 frontend (client/) that renders pages, components, and implements API routes.
• A NestJS backend (server/) exposing a REST API, using Prisma ORM to persist data in a relational database (e.g., PostgreSQL).
• The app’s use case is to let authenticated users create, view, edit, and categorize financial transactions.
File-Structure Analysis
• Top-level:
• client/ – Next.js 13 “app” directory with pages, API route handlers under client/app/api, React UI components under client/components, config files (tsconfig.json, next.config.ts), and static assets (public/).
• server/ – NestJS application with modules (auth, users, transactions, categories), DTOs, controllers, services, Prisma schema + migrations, and test suite.
• Architectural patterns:
• Frontend uses the Next.js App Router, Server Components, and API Routes (route.ts files) to handle client-side navigation and to proxy API calls.
• Backend follows NestJS’s modular MVC pattern: Controllers → Services → (Prisma) ORM → Database.
• Deployment/config: GitHub Workflows, ESLint, Prettier, build scripts, Prisma migrations.
Key Insights from the README
• The README simply names the project (“finance-tracker-app”), so the structure itself reveals the intended architecture: full-stack with separate client and server codebases.