How abhishekprajapati1/talker works
Project type and purpose
• This is a full-stack, real-time chat web application (“Talker”) built with Next.js on the client side and NestJS on the server side.
• Purpose: enable user registration/login, manage a contact book, and provide real-time messaging via WebSockets, backed by a SQLite database through Prisma ORM.
File structure
• Top-level folders:
• backend/ – NestJS project using modules (auth, user, chat, contact, token, utility), Prisma (schema + migrations), controllers, services, guards, gateway for socket.io
• client/ – Next.js 13 (“app” directory) with React components, TailwindCSS, Redux Toolkit store, TanStack Query, socket.io-client, and utility libs for API calls & hooks
• Config files:
• backend/nest-cli.json, tsconfig.json/build; package.json, pnpm lock
• client/next.config.mjs, tailwind.config.ts, postcss.config.js, tsconfig.json, package.json, pnpm lock
• Patterns & modules:
• NestJS uses the modular architecture (each feature folder under src/ is a module)
• Prisma for database access and migrations
• REST controllers + WebSocket gateway (chat.gateway.ts)
• Next.js “app” routes for protected vs. auth pages; shared UI components & libs
README for additional insights
• Tech Stack callouts:
• Client: NextJS, Redux Toolkit, TailwindCSS, MUI, TanStack Query, Axios, DayJS, socket.io-client
• Server: NestJS + ExpressAdapter, SQLite, PrismaORM, Swagger, socket.io
• Features outline confirms contact book, real-time messaging, JWT rotation, double-layer auth (REST + WS)