How mahdita97/turborepo-boilerplate works
Project type and purpose
• This is a frontend-focused monorepo boilerplate using Turborepo.
• It hosts one Next.js “web” application and several shared packages (UI component library, ESLint configs, TypeScript configs, Tailwind config).
• Its purpose is to demonstrate how to structure a multi-package repo for building a consistent design system and web app with shared configs and components.
File structure
Top-level
• turbo.json → Turborepo pipeline definitions (task graph, caching)
• package.json → root scripts for workspace management
• tsconfig.json → base TypeScript settings
• .gitignore, README → repo-wide metadata
apps/web
• Next.js + Tailwind site
• next.config.js uses transpilePackages to compile shared UI on build
• src/app contains layout, pages, global CSS
packages/
• ui → React component library (TSX + Tailwind)
• config-eslint → shared ESLint configurations
• config-typescript → shared tsconfig variants (base, nextjs, react-library)
• tailwind-config → single Tailwind config consumed by both app + UI
Extract architecture notes from the README
• Build “ui” into dist but consume via Next.js compiler
• Share one Tailwind config to avoid class collision
• Leverage Turborepo to orchestrate build/lint/test across all workspaces
Main components
a. Turborepo Orchestrator (root)
• Defines task pipelines (build/ui → build/web → test)
• Caches outputs, parallelizes tasks
b. apps/web (Next.js application)
c. packages/ui (shared React + Tailwind component library)
d. Shared config packages
– config-eslint (lint rules)
– config-typescript (TS project references)
– tailwind-config (CSS utility settings)
e. External ecosystems
– npm/Yarn (package registry)
– daisyUI & daisyUI-React (third-party UI plugins)
Relationships & interactions
• apps/web imports UI components (packages/ui)
• Both apps/web and packages/ui extend tailwind-config for styling
• Both codebases extend config-eslint and config-typescript via “extends” in their respective config files
• Turborepo triggers:
• build: ui → dist
• build: web (with transpilePackages(ui))
• lint/test across all workspaces
Architectural patterns & design principles
• Monorepo pattern with Turborepo for cross-package orchestration
• Shared configuration via dedicated config packages to enforce consistency
• Component library (packages/ui) as single source of truth for UI elements
• Tailwind “content” scanning strategy centralized in tailwind-config
• Component boundaries: root vs. apps vs. packages
• Data/asset flows: build outputs, tailwind CSS generation, transpilation
• External plugin dependencies: daisyUI, npm registry
• Highlights Turborepo’s orchestration role
• Shows how the Next.js app consumes the shared UI library and configs
• Depicts the monorepo’s shared-config strategy and build pipeline
You capture every package as its own component, group related items, and annotate interactions to avoid ambiguity.