ShadCN UI in 2026: the component library that changed how we build UIs

shadcn/ui changed how I think about component libraries. After using it across 4 production projects, here's what makes it different and when it's the right choice. It's not a library. It's a collection. The core insight: shadcn/ui doesn't install into node_modules . You copy components directly into your project. Each component is a single file in your components/ui/ directory that you own and can modify. npx shadcn@latest init npx shadcn@latest add button npx shadcn@latest add dialog npx shadcn@latest add dropdown-menu After running these commands, you have: components/ui/ button.tsx # You own this file dialog.tsx # Modify it however you want dropdown-menu.tsx No import { Button } from '@shadcn/ui' . Instead: import { Button } from '@/components/ui/button' . The component is your code now. Why this matters in practice 1. No version lock-in With a traditional library (MUI, Chakra, Mantine), upgrading from v4 to v5 is a project in itself. Breaking changes cascade through your entire ap