How papysaliou/nestjs_ecommerce_backend works
Project type and purpose
• This is a backend-only RESTful API built on NestJS (a Node.js framework in TypeScript).
• It exposes CRUD endpoints for “produits” (products) and “categories,” and handles authentication (users, profiles, JWT-based guards).
• It uses SQLite (db.sqlite) as its data store and follows Nest’s module-controller-service pattern.
File structure
• Top-level files:
– package.json, tsconfig.json, nest-cli.json → Node/Nest build and run configuration
– db.sqlite → embedded database
• src/main.ts → application entry point (bootstraps Nest application)
• src/app.module.ts → root module importing all feature modules
• src/auth → authentication module: controller, service, entities (User, Produit), JWT strategy and guard
• src/categorie → category module: controller, service, entity, DTOs
• src/produit → product module: controller, service
• src/app.controller.ts, app.service.ts → example root controller/service (starter code)
• test → end-to-end test setup
Key insights from README
• Confirms NestJS framework, intended as a server-side starter repository.
• No frontend; focus on building and deploying the API.
Detailed element checklist
• Every module and its subcomponents (Controller, Service, Entity)
• The bootstrap flow (main.ts → AppModule)
• The Database connection (TypeORM, SQLite)
• The JWT authentication flow (AuthController → AuthService → JwtStrategy → Guard)
• Inter-module imports and dependencies