Module Graph
Auto-generated from the NestJS source. Do not edit by hand — run
scripts/gen-docs.sh.
The Pond API is composed of a root AppModule that imports ConfigModule, a single Mongoose connection, and one feature module per resource.
Modules
AppModule
Root Nest module for the Pond API. Composes: - ConfigModule (global) — exposes process.env through ConfigService. MONGO_URI and PORT live in api/.env. - MongooseModule.forRootAsync — the single Mongoose connection. Reads MONGO_URI via getOrThrow so a missing env var fails fast at boot instead of producing mysterious connection errors on the first request. - UsersModule and RolesModule — feature modules. Each registers its own schema via MongooseModule.forFeature and exposes a controller + service + typed DTOs.
- Source:
api/src/app.module.ts - Imports:
ConfigModule,MongooseModule,UsersModule,RolesModule
RolesModule
Feature module for the Role resource. Mirrors UsersModule. Registers the Mongoose schema via MongooseModule.forFeature and exposes the controller and service. The service is exported so other modules can inject it (e.g. when a future module needs to cascade role changes to users).
- Source:
api/src/roles/roles.module.ts - Imports:
MongooseModule - Controllers:
RolesController - Providers:
RolesService - Exports:
RolesService
UsersModule
Feature module for the User resource. Registers the Mongoose schema via MongooseModule.forFeature and exposes UsersController and UsersService. The service is exported so other modules can inject it; the controller is internal-only as far as Nest is concerned.
- Source:
api/src/users/users.module.ts - Imports:
MongooseModule - Controllers:
UsersController - Providers:
UsersService - Exports:
UsersService