How tbarondar/capynotes works
Main components
• Frontend (browser + Next.js App Router pages & React components)
• API Layer
– NextAuth “/api/auth” routes for authentication
– tRPC “/api/trpc” route handler
• Business Logic Layer (tRPC routers in server/routers)
• Data Access Layer (Prisma client connecting to PostgreSQL)
• Database (PostgreSQL)
Relationships and data flows
• Browser renders React components (app/, components/)
↓ uses tRPC client (app/_trpc/client.ts) and NextAuth client (auth.ts)
• tRPC client → Next.js API route /api/trpc → tRPC server (server/trpc.ts)
• NextAuth client ↔ NextAuth route handler (app/api/auth/[...nextauth]/route.ts)
• tRPC resolvers (server/routers/*.ts) call Prisma client (prisma/client.ts)
• Prisma client speaks to the Postgres database (schema in prisma/schema.prisma)
Architectural patterns
• Monorepo structure with clear separation:
– app/ for UI and API route handlers
– server/ for API router definitions and business logic
– prisma/ for schema and migrations
• tRPC for typesafe end-to-end RPCs
• NextAuth for session management
• Prisma ORM for database modeling and migrations
Call out major technologies and layers
• Next.js App Router, React, CSS Modules
• tRPC (client.ts, Provider.tsx, server/trpc.ts)
• NextAuth (app/api/auth route)
• Prisma ORM + migrations → PostgreSQL
• TypeScript for all layers