Does shadcn/ui support tree shaking in a monorepo setup?

[fahrulalwan]

I have a question about the expected tree shaking behavior when using a shared shadcn/ui component library within a Turborepo monorepo.

Context

My project is structured as a monorepo with a shared UI library and multiple applications.

Monorepo Structure:

monorepo/
├── apps/
│   ├── app-a
│   ├── app-b
│   └── app-c
└── libs/
    └── my-shadcn-lib

The my-shadcn-lib contains several components built with shadcn/ui:

my-shadcn-lib/
├── component-a
├── component-b
├── component-c
├── component-d
├── component-e
└── component-f

Each application only imports the specific components it needs from my-shadcn-lib.

• app-a imports component-a and component-b.
• app-b imports component-c and component-d.
• app-c imports component-e and component-f.

Question

When I build a specific application (e.g., app-a), will the final production bundle only include the code for the components it explicitly imports (component-a and component-b)?

Or, will the bundle include all components (component-a through component-f) from the entire my-shadcn-lib library?

assuming app-a & app-b are using next.js and app-c is using vite.

[oluwatunmiisheii]

Tree shaking will work fine here. When you build app-a, only component-a and component-b (plus their direct dependencies) make it into the bundle. Components c–f are excluded since they’re never imported. Both Next.js (Webpack/Turbopack) and Vite (Rollup) handle this automatically. Just make sure your shared lib is ESM