mwanago/nestjs-typescript

Purpose and Runtime

This is a TypeScript/NestJS backend starter expanded into a multi-domain API platform: users/authentication, content, catalog, payments, messaging, files, and operations. It runs on Node.js; bootstrap and application composition are in src/main.ts and src/app.module.ts. src/repl.ts provides a separate interactive Nest application entry point.

Application Composition and Transport Boundaries

src/app.module.ts is the dependency-composition root, wiring feature modules around shared database, logging, search, PubSub, and health capabilities. Most domain APIs use REST controllers, while posts also expose GraphQL through src/posts/posts.resolver.ts and the generated schema src/schema.gql. Real-time chat is a gateway boundary in src/chat/chat.gateway.ts; subscribers define a protobuf contract at src/subscribers/subscribers.proto, indicating a service/RPC integration boundary.

Persistence and Operational Cross-Cutting Layer

Database-backed entities are distributed by domain, with infrastructure rooted in src/database/database.module.ts and database logging in src/database/databaseLogger.ts. Core persisted aggregates include users (src/users/user.entity.ts), posts (src/posts/post.entity.ts), and Stripe webhook events (src/stripeWebhook/StripeEvent.entity.ts). Cross-cutting request processing includes logging middleware (src/utils/logs.middleware.ts), raw-body handling for signed webhook verification (src/utils/rawBody.middleware.ts), and null-value response normalization (src/utils/excludeNull.interceptor.ts).

Identity, Authorization, and Account Verification

Authentication is centered on src/authentication/authentication.service.ts and exposed through src/authentication/authentication.controller.ts. It supports local credentials plus JWT access, refresh, and two-factor strategies/guards, with authorization boundaries implemented in src/authentication/jwt-authentication.guard.ts and src/authentication/jwt-refresh.guard.ts. Account lifecycle extends to email verification (src/emailConfirmation/emailConfirmation.service.ts), Google authentication (src/googleAuthentication/googleAuthentication.service.ts), and SMS/two-factor verification (src/sms/sms.service.ts).

Content, Query, and Caching Flow

Posts are the richest content domain: REST and GraphQL requests enter src/posts/posts.controller.ts or src/posts/posts.resolver.ts, then flow through src/posts/posts.service.ts to persistence. Search is separated into src/posts/postsSearch.service.ts, with Elasticsearch explicitly represented by src/health/elasticsearchHealthIndicator.ts. HTTP cache behavior is scoped to posts in src/posts/httpCache.interceptor.ts. Comments use CQRS-style command/query dispatch, with write and read handlers at src/comments/commands/handlers/create-comment.handler.ts and src/comments/queries/handlers/getComments.handler.ts.

Commerce and External Payment Processing

Product catalog management is divided between product categories and products: src/productCategories/productCategories.service.ts and src/products/products.service.ts. Payment operations are mediated by src/stripe/stripe.service.ts; charge and saved-card HTTP endpoints are in src/charge/charge.controller.ts and src/credit-cards/creditCards.controller.ts. Stripe callbacks enter the dedicated webhook controller/service boundary (src/stripeWebhook/stripeWebhook.controller.ts, src/stripeWebhook/stripeWebhook.service.ts), which requires raw request bodies and records webhook events.

Communications, Files, and Background-Facing Services

Email delivery and scheduling are distinct capabilities in src/email/email.service.ts and src/emailScheduling/emailScheduling.service.ts; SMS is handled separately. File metadata/storage is modeled through src/files/files.service.ts, while local upload handling is isolated in src/localFiles/localFiles.service.ts. Image optimization is exposed as a dedicated processing boundary in src/optimize/image.processor.ts. docker-compose.yml is the repository’s infrastructure orchestration entry point; Elasticsearch is materially implied by the search and health components.