How macksimbondarew/fullstack-auth works
Project type and purpose
• This is a full‑stack web application.
• Frontend: Next.js (React + TypeScript)
• Backend: NestJS (Node.js + TypeScript)
• ORM/DB layer: Prisma (PostgreSQL)
• Features: user registration/login, email confirmation, password recovery, two‑factor authentication, OAuth social login
File structure
• Top‑level directories:
• frontend/ → a Next.js “app”‑directory project with feature slices under src/app and src/features
• nestjs-server/ → a modular NestJS server with controllers, services, DTOs, Prisma schema and generated client
• Frontend patterns:
• src/app for route‑based pages (auth, dashboard, settings, etc.)
• src/features for domain logic (auth, user) using hooks, services, schemes, component libraries
• src/shared for cross‑cutting pieces: API client, UI components, providers (TanStack Query, theme, toast), utils
• Backend patterns:
• Nest modules: auth (with sub‑modules: email‑confirmation, password‑recovery, provider/OAuth, 2FA), user, prisma, mail, common libs
• Layered MVC: controllers → services → Prisma ORM → database
• Config files for mailer, session, recaptcha, OAuth providers
Key insights (README is blank, so inferred from structure)
• REST API with JSON payloads
• External dependencies: SMTP/email service, OAuth providers (Google, Yandex), reCAPTCHA