How hopscotcher/dekut-marketplace works
Project Type and Purpose
• This is a full-stack Next.js (App Router) e-commerce/marketplace application.
• It provides client-side React pages (product listings, search, sell form, user dashboard) and serverless API routes (CRUD for products, user & bulk operations).
• It uses Prisma as the ORM for database access, React Query (via queryClient) for data fetching/caching, and custom UI components.
High-Level Architectural Components
a. Client Layer (Next.js Pages & Components)
– src/app: React server & client components for pages (/, /products, /categories, /search, /sell, /user/dashboard).
– src/components: reusable UI blocks (common, features, product form, layout, search filters).
– src/contexts & src/stores: global state providers (ProductContext, UserContext) and Zustand store (searchStore).
– src/hooks & src/lib/queryClient: custom hooks for data operations and React Query setup.
b. Server Layer (API Routes & Services)
– src/app/api: Next.js serverless route handlers → route.ts for /api/products, /api/users, including bulk and nested routes.
– src/services: business logic for CRUD operations (productService).
c. Data Access Layer (Prisma & Database)
– prisma/schema.prisma & prisma/seed.ts: ORM schema definitions and seed script, connecting to a relational database (e.g. PostgreSQL).
d. Static & Configuration
– public: static assets.
– next.config.ts, postcss.config.mjs, eslint.config.mjs: build, styling, linting configurations.
– package.json & tsconfig.json: dependencies & TypeScript config.
Component Interactions and Data Flow
• User Browser → Next.js Client (React Pages & Components)
↳ Calls React Query hooks → src/services → fetch() → Next.js API Routes
• Next.js API Routes → src/services → Prisma Client → Database
• Responses bubble back: Database → Prisma → service returns JSON → API route → React Query → UI updates.
• Global State (contexts/stores) synchronizes UI components (e.g., searchStore for filters, UserContext for auth state).
Architectural Patterns & Principles
• Layered Architecture: Presentation → Business Logic → Data Access
• Serverless Functions: Next.js API routes as micro-endpoints
• Client-side Data Caching: React Query (queryClient)
• ORM Abstraction: Prisma for type-safe DB access
• Modular UI: Atomic/common components + feature-specific components