How amanzaildarr/nest-graphql-typeorm-postgresql works
Project type and purpose
• This is a NestJS-based Node.js server–side application. It follows Nest’s modular architecture and uses TypeScript, TypeORM for database access, and has a “user” domain module. It provides a GraphQL/REST resolver in user.resolver.ts (by default Nest could be REST, but the naming “resolver” suggests GraphQL).
File structure
• Top level:
• package.json / tsconfig.json / nest-cli.json – project configuration and build.
• src/main.ts – Nest application bootstrap.
• src/app.module.ts – root module that imports other modules and providers.
• database.provider.ts and src/typeorm/typeorm.service.ts – custom database providers and TypeORM configuration.
• src/i18n – internationalization resources.
• src/user – user domain module, subdivided into database, dto, entities, resolver, service, module.
• test folder – end-to-end tests using Jest.
• Environment configuration: env.sample.
README for additional insights
• We know it’s intended for a scalable, modular server application.
Detail
• Module and its subcomponents (e.g., user.resolver, user.service, user.entity).
• Injection graph: which provider is injected into which module.
• Inside that, subdivide AppModule into:
• TypeORM Provider (database.provider.ts & typeorm.service.ts).
• i18n Provider (src/i18n).
• UserModule (with its Resolver, Service, Entities).