How ikaushiksharma/costkeeper works
Project type and purpose
• This is a full-stack, Next.js 13 application (using the new App Router) that implements a personal finance dashboard (accounts, categories, transactions, summary, settings).
• It bundles a React-based front end with server-side API routes, PWA/offline support, and a relational database (via Drizzle ORM).
File structure
• Top-level “app” directory houses both UI pages (app/(auth), app/(dashboard), app/offline) and API routes (app/api/…/route.ts).
• “components”, “features” and “providers” contain React UI elements, domain-specific hooks and context providers (e.g., React Query, theming, sheet modals).
• “db” and “drizzle.config.ts” configure the database schema and Drizzle ORM.
• Service worker and PWA assets live under “public” (sw.js, workbox).
• Build/configuration files: next.config.js, tailwind.config.ts, bun.lockb (uses Bun), ESLint/Husky/prettier for linting/formatting.
Readme insights
• (empty README, but file names convey architecture: App Router, API routes, Drizzle for data persistence, Hono middleware, PWA support)
Zone A: Client
• Browser
• UI Routes (pages)
• React Query Provider
• Feature Hooks & Components
• Service Worker (intercepts requests)
Zone B: Server
• Next.js App Router (SSR/SSG)
• API Routes (/app/api/…/route.ts)
• Middleware (Hono, auth checks)
Zone C: Persistence
• Drizzle ORM layer
• SQL Database
Zone D: Dev / Build Tools (optional overlay)
• Bun runtime
• Tailwind
• ESLint/Husky/Prettier