shadcn Release Notes

Minor Changes

#11501 aef1cdca54e8da689351cdddf959342909e45e76 Thanks @shadcn! - merge registries from package.json and components.json, and support adding registries to package.json when components.json is not present

Patch Changes

#11500 e66b99b14dd9c54afc434dbf5a702f170b1153b0 Thanks @shadcn! - Skip unreadable directories during file scans instead of failing with EACCES.

#11504 9f4e3ff26025d16a243ea03cc891c734c4cf0b59 Thanks @shadcn! - Skip unreadable directories when resolving monorepo targets.

#11502 87d71b3629c34f3c38a353a211ec8591c1ff1721 Thanks @shadcn! - resolve registries declared in package.json when adding components. shadcn add, search, view and init now resolve registries from package.json in memory without persisting them to components.json

#9248 03c45b822e60195796dfd3d2fcf7c223ff4ece86 Thanks @Grafikart! - Fix shadcn for projects with unreadable permission files

Minor Changes

#10453 deda4df80fb350230b2fce2b575e769a90cae076 Thanks @nbouvrette! - Add SOCKS4/SOCKS5 proxy support to the registry HTTP stack via ALL_PROXY=socks5://... (the curl convention), backed by the socks package.

Proxy selection now goes through a createProxyDispatcher(env) factory that checks ALL_PROXY / all_proxy for a socks*:// URL before falling back to the existing HTTP/HTTPS handling. ALL_PROXY with a non-SOCKS scheme is ignored here — HTTP_PROXY / HTTPS_PROXY remain the way to configure those. Existing HTTPS_PROXY / HTTP_PROXY / NO_PROXY handling via undici.EnvHttpProxyAgent is unchanged.

Today, we're releasing Questionnaire, a new component for multi-step question flows. Use it for agent clarification prompts, onboarding, surveys, intake forms, and configuration.

Questionnaire is available for Base UI, React Aria, and Radix across all eight styles.

Features

• Single and multiple selection with native radios and checkboxes.
• Freeform answers alongside fixed choices.
• Explicit skipping for optional questions.
• Previous, next, submit, and custom progress controls.
• Required and custom validation.
• Controlled navigation, saved defaults, and conditional questions.
• Keyboard navigation with optional letter or number shortcuts.
• Native form serialization and server-rendered collection state.
• Standalone, Card, and Dialog composition.

Installation

pnpm dlx shadcn@latest add questionnaire

@shadcn/react

The component is also available as an unstyled headless primitive in @shadcn/react. Read the docs to learn more.

View Questionnaire

Patch Changes

• #11196 c49c3061b5b86b130736d36bf20008349f89b416 Thanks @shadcn! - Drop custom registry headers on cross-origin redirects to prevent credential leakage.
• #11191 df2656111fc8ca030eb768ade2da26cef2fd11b5 Thanks @shadcn! - Validate file paths for registry items without an explicit target to prevent path traversal.
• #11195 b8a8e9209659fa810514b61c60ad593bc81973f9 Thanks @shadcn! - Prevent flag injection from registry-supplied dependency strings during install.
• #11208 2b89d67e19ceda27381477e127b349f9aaa25355 Thanks @shadcn! - Add React Aria support.

Starting today, Base UI is the default component library in shadcn/ui.

First, a bit of history. When shadcn/ui launched in January 2023, it was built on Radix. At the time, nothing else came close. Unstyled headless components, great APIs, great accessibility, battle-tested in millions of apps.

Fast forward a few years and the same folks who built Radix are building something new: Base UI. They've done it once. Now they get to do it again, with everything they learned the first time.

Last year, Base UI tagged a beta and a lot of you asked if we are going to replace Radix with it. I said "the worst thing you can do for your production app is switch component libraries". I meant it, and it still holds. So instead of switching, we did the shadcn thing: we rebuilt every component for Base UI, kept the same abstraction, and let you choose. December brought npx shadcn create with both libraries. January brought full Base UI docs.

Then we watched what you did with it.

Why Now

• Base UI is stable. It's at 1.6.0 with 6M+ weekly downloads.
• It keeps getting better. The team ships new and useful components regularly.
• We use it. Every new project we've started runs on Base UI.
• You use it. Projects created on shadcn/create now pick Base UI over Radix 2 to 1.

The community already made the call. We're making it official.

What's Changed

• New projects default to Base UI. Run npx shadcn init and Base UI is the default pick.
• shadcn/create shows Base UI first.
• The docs default to Base UI. Component pages open on the Base UI tab. Radix docs are one click away.

What This Means for You

Radix is not being deprecated. We still support it, and every update and new component will ship for both libraries (unless a component only exists in Base UI).

You do not need to migrate. Radix is a mature, tested library. We still run it in production today and we're not migrating. If your app works, keep shipping.

Prefer Radix for new projects? It's one flag away:

pnpm dlx shadcn init -b radix

If you have scripts or CI running shadcn init non-interactively and expecting Radix, add -b radix to keep them on the same path.

Building a registry? Ship a registry:base config if you want to pin a specific library. Items without one now init as Base UI.

Starting something new? We recommend Base UI.

When You're Ready to Migrate

You don't need to migrate. But if you want to, we built a skill for it:

pnpm dlx skills add shadcn/ui

Then ask your coding agent:

migrate accordion to base-ui

It's progressive by default: migrate one component and its usage at a time while your project stays green and shippable. Both libraries coexist while you work. Stop halfway, ship, come back next week and it picks up where you left off. Or ask for the whole project in one go.

Why a skill and not a codemod?

Because you own the code. You've added variants, changed classes, threaded new props. A codemod handles the components you never touched and breaks on the ones you did.

So we shipped knowledge instead: every rename, every prop change, every behavior difference, hand-checked against both libraries. Your agent reads it, figures out what you changed, and carries those changes over.

Mechanical things get fixed everywhere (asChild is now render). Behavior changes get flagged, never silently patched. You decide.

What a migration produces

Every run leaves three things:

• Working code. Typechecked and built before it reports success.
• A report per component in .migration/ at your project root: what changed, what was left alone, and a short checklist of things to verify by hand.
• Clean git history. One commit per component, on a branch. Rollback is deleting the branch.

Here's what a report looks like:

.migration/accordion.md

No hidden state. Progress lives in your files and git history, so any agent, any session, any day picks up where the last one stopped.

It works with Claude Code, Cursor, or any agent that supports skills. We tested it on real projects: 60+ components, 36 of them on Radix. A full migration ran in about 25 minutes at roughly 10k tokens per component. Clean builds, customizations intact.

Patch Changes

• #11106 f6a26478547c7057aeda82516666dc3473dc39bd Thanks @shadcn! - Fix MessageScroller autoScroll around anchored turns: the anchor hold now hands off to follow-output once the streamed reply fills the viewport, content growth outrunning the frame-coalesced resize handler no longer releases follow-output, and the scroll button no longer flickers while follow-output closes the gap a streamed chunk just opened.
• #11100 dd6ce77cf1606eee2839368a97cc35417f763232 Thanks @shadcn! - Fix MessageScroller abandoning a newly appended scrollAnchor placement when autoScroll is enabled, so the anchored turn holds at the reading line while the reply streams.
• #11085 628e427231ca4bb7f586a69f99fe7809749a53e2 Thanks @devnomic! - Fix MessageScroller firing "ResizeObserver loop completed with undelivered notifications" during streamed content growth by coalescing ResizeObserver callbacks into requestAnimationFrame.