← Back to all sparks
S

shadcn/ui

DESIGN
Velocity7.5

Open-source React component library

shadcn stops being one component library and becomes a layer over several bases.

component-registryreact-ariabase-uitypographydistribution-model
Current state
July and August produced a release almost every week. React Aria joined Base UI as a component base, a typography system shipped as its own project, a helpers package appeared aimed at AI SDK and TanStack AI, and registries gained server-side search. New components — Toast, Questionnaire — arrive alongside all of it, but they are no longer the main story.
Where it's heading
The centre of gravity is moving from components to the layer underneath them. Supporting more than one primitive base means shadcn's value is the API and distribution model rather than any particular headless library, and server-side registry search means the registry is being treated as infrastructure other people run. The helpers and typeset packages extend the same idea outward: small owned pieces of an app, distributed the way components already are.
Prediction
Expect more of the surface to be split into separately installable pieces, and more work on the registry as a system others operate — with new components continuing at the current pace but carrying less weight than the platform changes around them.

Recent moves

  1. 5d ago

    Questionnaire: a component for multi-step question flows

    A component for multi-step question flows with fixed, freeform, multiple and skippable answers. Larger in scope than a typical primitive — this is a flow, not a control — which fits the pattern of shadcn shipping bigger composed pieces.

    View source ↗
  2. 10d ago

    Registries can now handle search server-side

    Registry search moves to the server, which matters for anyone running their own registry at size rather than consuming the public one. Part of the steady work turning the registry from a file format into infrastructure.

    View source ↗
  3. 18d ago

    A new Toast component built on Base UI primitives

    Toast arrives on Base UI, continuing the migration of components onto that primitive set. Routine on its own, but it is the accumulation of these that makes multiple bases a real capability rather than an announcement.

    View source ↗
  4. 24d ago

    React Aria becomes an available component base

    ⚡ SPARK

    React Aria joins Base UI as a base shadcn components can be built on. It changes what shadcn is: not a library bound to one headless primitive set, but a distribution layer that can sit over several — which is the architecture everything else this month builds on.

    View source ↗
  5. 27d ago

    @shadcn/helpers ships utilities for AI SDK and TanStack AI

    A separate package of small, focused helpers for app development, opening with AI SDK and TanStack AI support. The choice of what to start with says where the project expects its users to be building.

    View source ↗
  6. 1mo ago

    shadcn/typeset: a typography system in one CSS file you own

    ⚡ SPARK

    A complete typography system for HTML — spanning static content and streaming chat output — shipped as a single CSS file distributed under the same own-the-code model as the components. It extends shadcn's distribution approach past React entirely.

    View source ↗