How nambui98/mtd-tax works
Project type and purpose
• This is a full-stack monorepo for a SaaS-style application.
• apps/web: Next.js (App Router) frontend with Tailwind and shadcn/UI components.
• apps/api: NestJS backend exposing REST endpoints, modules for auth, users, clients, documents, HMRC integration, uploads (S3), mailing, roles.
• packages/ui: shared React UI library.
• packages/database: Drizzle ORM setup, migrations and seeds.
• Monorepo tooling: pnpm workspaces, Turbo, shared ESLint/TS configs.
File structure
• Top-level “apps” directory splits frontend vs. backend.
• “packages” holds shared libraries (UI, DB migration/ORM, config presets).
• API uses NestJS’s module structure (auth, users, clients, etc.).
• Web uses Next.js App folder, NextAuth route, shared “components”, “services/api.ts” client.
• Config files at root (docker-compose.yml, turbo.json, pnpm-workspace.yaml) define dev and deploy orchestration.
• DB migrations in packages/database/drizzle, Drizzle CLI for schema management.
README for additional insights
• Confirms use of shadcn components in apps/web via packages/ui.
• Tailwind is configured for the UI package.
• Drizzle CLI commands available for generating and running migrations.
Detail
– Show shared config layers (environment variables, .env, configuration.ts).
– If relevant, overlay CI/CD or Docker Compose orchestration.