06/02/2026
shadcn's May release added registry composition and a shadcn registry validate command. Authors can now split a large component registry across multiple files and check the whole thing for schema errors, duplicate names, and broken paths before publishing.
This is design systems growing up. The registry becomes real distribution infrastructure, not a folder you hope stays consistent.
It maps directly to how we work. We build and maintain design systems and component libraries for clients, often shared across a partner agency's projects. Validation before publish means a token rename or a moved file gets caught at build time, not in someone else's production app.
Component ownership has always been the appeal here. Tooling that keeps a growing registry trustworthy is what makes that ownership scale.
Read more: shadcn/ui Registry Include and Validate
Organize and validate source registries.