Turborepo Design System Starter

This is a community-maintained example. If you experience a problem, please submit a pull request with a fix. GitHub Issues will be closed.

This guide explains how to use a React design system starter powered by:

• 🏎 Turborepo — High-performance build system for Monorepos
• 🚀 React — JavaScript library for user interfaces
• 🛠 Tsup — TypeScript bundler powered by esbuild
• 📖 Storybook — UI component environment powered by Vite

As well as a few others tools preconfigured:

• TypeScript for static type checking
• ESLint for code linting
• Prettier for code formatting
• Changesets for managing versioning and changelogs
• GitHub Actions for fully automated package publishing

Using this example

Run the following command:

1
npx create-turbo@latest -e design-system

Useful Commands

• pnpm build - Build all packages, including the Storybook site
• pnpm dev - Run all packages locally and preview with Storybook
• pnpm lint - Lint all packages
• pnpm changeset - Generate a changeset
• pnpm clean - Clean up all node_modules and dist folders (runs each package's clean script)

Turborepo

Turborepo is a high-performance build system for JavaScript and TypeScript codebases. It was designed after the workflows used by massive software engineering organizations to ship code at scale. Turborepo abstracts the complex configuration needed for monorepos and provides fast, incremental builds with zero-configuration remote caching.

Using Turborepo simplifies managing your design system monorepo, as you can have a single lint, build, test, and release process for all packages. Learn more about how monorepos improve your development workflow.

Apps & Packages

This Turborepo includes the following packages and applications:

• apps/docs: Component documentation site with Storybook
• packages/ui: Core React components
• packages/typescript-config: Shared tsconfig.jsons used throughout the Turborepo
• packages/eslint-config: ESLint preset

Each package and app is 100% TypeScript. Workspaces enables us to "hoist" dependencies that are shared between packages to the root package.json. This means smaller node_modules folders and a better local dev experience. To install a dependency for the entire monorepo, use the -w workspaces flag with pnpm add.

This example sets up your .gitignore to exclude all generated files, other folders like node_modules used to store your dependencies.

Compilation

To make the ui library code work across all browsers, we need to compile the raw TypeScript and React code to plain JavaScript. We can accomplish this with tsup, which uses esbuild to greatly improve performance.

Running pnpm build from the root of the Turborepo will run the build command defined in each package's package.json file. Turborepo runs each build in parallel and caches & hashes the output to speed up future builds.

For @acme/ui, the build command is equivalent to the following:

1
tsup src/*.tsx --format esm,cjs --dts --external react

tsup compiles all of the components in the design system individually, into both ES Modules and CommonJS formats as well as their TypeScript types. The package.json for @acme/ui then instructs the consumer to select the correct format:

1
{
2
  "name": "@acme/ui",
3
  "version": "0.0.0",
4
  "sideEffects": false,
5
  "exports":{
6
    "./button": {
7
      "types": "./src/button.tsx",
8
      "import": "./dist/button.mjs",
9
      "require": "./dist/button.js"
10
    }
11
  }
12
}

Run pnpm build to confirm compilation is working correctly. You should see a folder ui/dist which contains the compiled output.

1
ui
2
└── dist
3
    ├── button.d.ts  <-- Types
4
    ├── button.js    <-- CommonJS version
5
    ├── button.mjs   <-- ES Modules version
6
    └── button.d.mts   <-- ES Modules version with Types

Components

Each file inside of ui/src is a component inside our design system. For example:

1
import * as React from 'react';
2

3
export interface ButtonProps {
4
  children: React.ReactNode;
5
}
6

7
export function Button(props: ButtonProps) {
8
  return <button>{props.children}</button>;
9
}
10

11
Button.displayName = 'Button';

When adding a new file, ensure that its specifier is defined in package.json file:

1
{
2
  "name": "@acme/ui",
3
  "version": "0.0.0",
4
  "sideEffects": false,
5
  "exports":{
6
    "./button": {
7
      "types": "./src/button.tsx",
8
      "import": "./dist/button.mjs",
9
      "require": "./dist/button.js"
10
    }
11
    // Add new component exports here
12
  }
13
}

Storybook

Storybook provides us with an interactive UI playground for our components. This allows us to preview our components in the browser and instantly see changes when developing locally. This example preconfigures Storybook to:

• Use Vite to bundle stories instantly (in milliseconds)
• Automatically find any stories inside the stories/ folder
• Support using module path aliases like @acme/ui for imports
• Write MDX for component documentation pages

For example, here's the included Story for our Button component:

1
import { Button } from '@acme/ui/button';
2
import { Meta, Story, Preview, Props } from '@storybook/addon-docs/blocks';
3

4
<Meta title="Components/Button" component={Button} />
5

6
# Button
7

8
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec euismod, nisl eget consectetur tempor, nisl nunc egestas nisi, euismod aliquam nisl nunc euismod.
9

10
## Props
11

12
<Props of={Box} />
13

14
## Examples
15

16
<Preview>
17
  <Story name="Default">
18
    <Button>Hello</Button>
19
  </Story>
20
</Preview>

This example includes a few helpful Storybook scripts:

• pnpm dev: Starts Storybook in dev mode with hot reloading at localhost:6006
• pnpm build: Builds the Storybook UI and generates the static HTML files
• pnpm preview-storybook: Starts a local server to view the generated Storybook UI

Versioning & Publishing Packages

This example uses Changesets to manage versions, create changelogs, and publish to npm. It's preconfigured so you can start publishing packages immediately.

You'll need to create an NPM_TOKEN and GITHUB_TOKEN and add it to your GitHub repository settings to enable access to npm. It's also worth installing the Changesets bot on your repository.

Generating the Changelog

To generate your changelog, run pnpm changeset locally:

1. Which packages would you like to include? – This shows which packages and changed and which have remained the same. By default, no packages are included. Press space to select the packages you want to include in the changeset.
2. Which packages should have a major bump? – Press space to select the packages you want to bump versions for.
3. If doing the first major version, confirm you want to release.
4. Write a summary for the changes.
5. Confirm the changeset looks as expected.
6. A new Markdown file will be created in the changeset folder with the summary and a list of the packages included.

Releasing

When you push your code to GitHub, the GitHub Action will run the release script defined in the root package.json:

1
turbo run build --filter=docs^... && changeset publish

Turborepo runs the build script for all publishable packages (excluding docs) and publishes the packages to npm. By default, this example includes acme as the npm organization. To change this, do the following:

• Rename folders in packages/* to replace acme with your desired scope
• Search and replace acme with your desired scope
• Re-run pnpm install

To publish packages to a private npm organization scope, remove the following from each of the package.json's

1
- "publishConfig": {
2
-  "access": "public"
3
- },