How ou9999-wdl/turborepo-test works
Project type and purpose
• This is a monorepo template primarily hosting two Next.js front-end applications (“web” and “web-admin”), a shared UI component library (shadcn/ui in packages/ui), plus several tooling/configuration packages (eslint-config, typescript-config) and a small utility library (packages/util).
• Purpose: speed up multi-app development by centralizing shared UI components, coding standards, and utilities, all orchestrated by pnpm workspaces and Turborepo.
File structure
• Top-level “apps” folder:
• apps/web – Next.js app for general users
• apps/web-admin – Next.js app for administration
• Top-level “packages” folder:
• packages/ui – Shared React/Tailwind UI components
• packages/util – Shared helper functions (e.g., date utils)
• packages/eslint-config & packages/typescript-config – Central linting and TS settings
• Root files: pnpm workspace config (pnpm-workspace.yaml), Turborepo config (turbo.json), lock file, lint/prettier configs.
README for additional insights
• Confirms monorepo is autogenerated by pnpm dlx shadcn@latest init
• Emphasizes adding UI components via a CLI into packages/ui and automatic Tailwind integration.
• Usage pattern: apps import UI components from @workspace/ui/components/....
Detail
• Every local package as its own component rather than lumping “packages” together.
• Root-level config files (tsconfig.json, .eslintrc.js, turbo.json) influencing the entire workspace.
• If desired, annotate that adding new shadcn/ui components happens via CLI and updates packages/ui.