🚀 Turborepo starter NextJS with Shadcn/UI & Tailwind CSS

Turborepo starter NextJS with Shadcn/UI & Tailwind CSS pre-configured for shared UI components powered by:

Note

This example uses pnpm as package manager.

📝 Using this example

Clone the repository:

git clone https://github.com/henriqpohl/turborepo-shadcn-ui-tailwindcss.git

Install dependencies:

cd turborepo-shadcn-ui-tailwindcss
pnpm install

📦 What's inside?

This Turborepo includes the following packages/apps:

Apps and Packages

docs: a Next.js app
@repo/ui: a stub React component library shared by applications inside of apps folder (🚀 powered by Shadcn/UI and Tailwind CSS)
@repo/eslint-config: eslint configurations (includes eslint-config-next and eslint-config-prettier)
@repo/typescript-config: tsconfig.jsons used throughout the monorepo

Each package/app is 100% TypeScript.

Utilities

This Turborepo has some additional tools already setup for you:

TypeScript for static type checking
ESLint for code linting
Prettier for code formatting

🏗️ Build

To build all apps and packages, run the following command:

cd turborepo-shadcn-ui-tailwindcss
pnpm build

💻 Develop

To develop all apps and packages, run the following command:

cd turborepo-shadcn-ui-tailwindcss
pnpm dev

🌐 Remote Caching

Turborepo can use a technique known as Remote Caching to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.

By default, Turborepo will cache locally. To enable Remote Caching you will need an account with Vercel. If you don't have an account you can create one, then enter the following commands:

cd turborepo-shadcn-ui-tailwindcss
npx turbo login

This will authenticate the Turborepo CLI with your Vercel account.

Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your Turborepo:

npx turbo link

ℹ️ Useful Links

Learn more about the power of Turborepo:

Learn more about Shadcn/UI:

🐞 Found a Bug?

Uh-oh, looks like you stumbled upon a bug? No worries, we're here to squash it! Just head over to our issues section on GitHub and let us know what's up.