3f:I[20710,["/_next/static/immutable/chunks/0canky51svn6b.js","/_next/static/immutable/chunks/0rl5h8dhy836r.js","/_next/static/immutable/chunks/2sdj56tpp03g5.js","/_next/static/immutable/chunks/1y8pn0gzktrzt.js","/_next/static/immutable/chunks/0zn2-9ug2mjr3.js","/_next/static/immutable/chunks/2ci3yx4g187_8.js","/_next/static/immutable/chunks/2lgz6luks0lse.js","/_next/static/immutable/chunks/1mdgeen1ytbcy.js","/_next/static/immutable/chunks/23102wv9y7snc.js","/_next/static/immutable/chunks/3dm4iqrw7k2cn.js"],"OrgReleaseList"] 40:T905,# August 2026 - Private GitHub Registries Install registry items from private GitHub repositories using the GitHub CLI or a token. **GitHub registries now work with private repositories.** In June, we made it possible to turn any public GitHub repository into a registry. Teams asked for the same thing for their internal code: design systems, feature kits, agent rules and conventions that should not be public. You can now install from private repositories. If you can read the repository, the CLI can install from it. pnpmnpmyarnbun ``` pnpm dlx shadcn@latest add acme/internal-toolkit/auth-kit ``` ## Zero configuration If you are logged in to the GitHub CLI, there is nothing to set up. ``` gh auth login ``` When a repository is not publicly readable, the CLI reads it through `gh` using your stored credentials. The token stays inside the GitHub CLI. It never enters the shadcn process. ``` ✔ Using gh credentials. ✔ Checking registry. ✔ Created 1 file: - lib/auth.ts ``` ## CI support Where the GitHub CLI is not installed, set `GH_TOKEN` or `GITHUB_TOKEN`: ``` GH_TOKEN=github_pat_xxx npx shadcn@latest add acme/internal-toolkit/auth-kit ``` We recommend a fine-grained personal access token scoped to the repository with **Contents: Read-only** access. ## Works with every command Private repositories work with the same commands as public GitHub registries. pnpmnpmyarnbun ``` pnpm dlx shadcn@latest list acme/internal-toolkit ``` pnpmnpmyarnbun ``` pnpm dlx shadcn@latest search acme/internal-toolkit --query auth ``` pnpmnpmyarnbun ``` pnpm dlx shadcn@latest view acme/internal-toolkit/auth-kit ``` pnpmnpmyarnbun ``` pnpm dlx shadcn@latest registry validate acme/internal-toolkit ``` ## How it works - Public repositories are read anonymously, exactly as before. No credentials are used and the GitHub CLI is never invoked. - The CLI tries anonymous access first and only uses your credentials when the repository is not publicly readable. - Private files are read through GitHub's Contents API, pinned to the resolved commit SHA. - A token from `GH_TOKEN` is only ever sent to `api.github.com`. Stored GitHub CLI credentials are read by `gh`, not by the CLI. See the [Private repositories](/docs/registry/github#private-repositories) docs for the full guide.41:T644,# August 2026 - Human in the Loop Mock paused tool calls, approvals, and continuations for the AI SDK with @shadcn/helpers. **@shadcn/helpers** can now mock human-in-the-loop flows for the AI SDK. A scripted conversation can pause for real user input, wait for an approval, and continue with whatever the user decided. Everything streams through the real `useChat` lifecycle, so your tool cards, approval prompts, and question flows behave exactly as they would in production. ``` import { createChat } from "@shadcn/helpers/ai-sdk" const chat = createChat() .user("Help me plan the next prototype.") .assistant(({ writer }) => { writer.text("A couple of questions before I start.") writer.tool("askQuestions", { input: { questions } }) }) .assistant(({ writer, toolCall }) => { writer.text( toolCall?.name === "askQuestions" && toolCall.output ? `Starting with ${toolCall.output.answers.direction}.` : "Starting now." ) }) ``` Pass `needsApproval` to pause behind the user's decision. The scripted output streams after approval, and denial streams automatically. ``` chat .assistant(({ writer }) => { writer.text("That will archive 3 drafts. I need your approval.") writer.tool("archiveDrafts", { input: { count: 3 }, needsApproval: true, output: { archived: 3 }, }) }) .assistant(({ writer, toolCall }) => { writer.text( toolCall?.approved ? "Archived 3 drafts." : "Okay, leaving them in place." ) }) ``` [Read the Docs](https://ui.shadcn.com/docs/helpers/ai-sdk#human-in-the-loop)42:T9a8,# August 2026 - Questionnaire A new component for building multi-step question flows with fixed, freeform, multiple, and skippable answers. Today, we're releasing [**Questionnaire**](/docs/components/base/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. Question 1 of 3 What should the agent build next? Choose a direction or describe another task. Tool call timelineShow what the agent ran and what came back.AApproval checkpointsAsk before sensitive or destructive actions.BSub-agent handoffsMake delegated work and results easier to follow.C Choose an answer to continue. What should every progress update include? Select all that apply, or skip this question. ProgressADecisionsBRisksCNext stepD Choose an answer or skip this question. When should work begin? Choose when the agent should begin the work. Start nowANext development cycleBAdd it to the backlogC Choose an answer to continue. PreviousSkipNextSave plan ``` "use client" import * as React from "react" ``` ## 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](/docs/react/questionnaire) to learn more. [ View Questionnaire ](/docs/components/base/questionnaire)43:T578,# July 2026 - React Aria React Aria is now available as a component base in shadcn/ui. **React Aria** is now a first-class component base in shadcn/ui. Build with React Aria Components alongside Base UI and Radix. Pick it in shadcn/create or initialize a project with `--base aria`. The CLI handles the dependencies, registry resolution, styles, and component installation. ## What's New# - **A first-class React Aria base** - Choose React Aria anywhere you can choose Base UI or Radix, including the CLI, presets, and shadcn/create. - **Full component documentation** - React Aria components have dedicated installation, usage, composition, examples, and API reference sections. - **All eight styles** - Use React Aria with Vega, Nova, Maia, Lyra, Mira, Luma, Rhea, or Sera. - **Base-specific output** - React Aria state selectors and dependencies are scoped to the Aria registry. Existing Base UI and Radix components are unchanged. ## Start with React Aria# Use the `aria` base when initializing a project: ``` pnpm dlx shadcn@latest init --base aria ``` Or choose **React Aria** in [shadcn/create](/create?base=aria). Once the project is initialized, `shadcn add` installs the React Aria implementation for each component. Base UI remains the default, and Radix remains fully supported. Existing projects stay on their current base. [ Create a React Aria project ](/create?base=aria)44:T910,# July 2026 - Introducing @shadcn/helpers Small, focused helpers for developing apps, starting with AI SDK and TanStack AI. We are open sourcing **@shadcn/helpers**, a new package for small, focused helpers that make developing apps easier. Starting with a helper for AI SDK and TanStack AI. It lets you write a conversation in code, then run it through the real `useChat` lifecycle without a model, API route, network request, or API key. Your UI receives native framework messages and streaming events, so reasoning, tool calls, loading states, and message components behave the same way they do in production. Here is a conversation written with the AI SDK helper: ```typescript import { createChat } from "@shadcn/helpers/ai-sdk" const chat = createChat() .user("What changed in this release?") .assistant("The release adds keyboard shortcuts and faster search.") .user("Can you check the full release notes?") .sleep(500) .assistant(({ writer }) => { writer.stepStart() // Reasoning. writer.reasoning("I should read the release notes first.") // Tool call. writer .tool("getReleaseNotes", { title: "Reading release notes", input: { version: "latest" }, }) .sleep(500) .output({ highlights: ["Keyboard shortcuts", "Faster search"], }) // Source. writer.sourceUrl({ title: "Release notes", url: "https://example.com/releases", }) // Response. writer.text("The release adds keyboard shortcuts and faster search.") }) ``` Pass its messages and transport to `useChat`: ```typescript import { useChat } from "@ai-sdk/react" const initialMessages = chat.get(0) const transport = chat.transport() export function Chat() { const { messages } = useChat({ messages: initialMessages, transport, }) } ``` The package includes two adapters: - [`@shadcn/helpers/ai-sdk`](/docs/helpers/ai-sdk) plugs into AI SDK's `useChat` as a transport. - [`@shadcn/helpers/tanstack-ai`](/docs/helpers/tanstack-ai) plugs into TanStack AI's `useChat` as a connection and streams real AG-UI events. Use it to build components, create previews and demos, write documentation, or test streaming interfaces with deterministic output and no backend dependency. [ Read the Docs ](/docs/helpers/ai-sdk)45:T435,# July 2026 - Introducing shadcn/typeset A complete typography system for HTML, from blog posts to streaming chat. One CSS file you own. Today we're releasing **shadcn/typeset**: a styling system for HTML and rendered markdown, in one CSS file. Your app renders the same HTML elements everywhere: headings, paragraphs, lists, tables, and code. You style them for your blog, then your docs, and now chat. Typeset lets you style them once, then tune the rhythm for each context. ```

{content}

``` Add one class and everything inside gets styled. Typeset follows the size of its container, uses your theme, and gives you three controls: size, leading, and flow. You can create as many typesets as you need. Use a tighter rhythm for chat and a roomier one for docs: ``` .typeset-chat { --typeset-leading: 1.6; --typeset-flow: 1em; } .typeset-docs { --typeset-size: 15px; --typeset-leading: 1.75; --typeset-flow: 1.5em; } ``` ```

{message}

{page}46:T12da,# July 2026 - Base UI as the Default New projects now use Base UI by default. Radix is still fully supported. 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](https://www.base-ui.com). 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: ```markdown # accordion ## Changed ## Left alone ## Behavior changes ## Verify by hand ``` 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.47:T107c,# June 2026 - Components for Chat Interfaces MessageScroller, Message, Bubble, Attachment, and Marker. Components for building chat interfaces. Today, we're releasing a new set of components for building chat interfaces: [**MessageScroller**](/docs/components/message-scroller), [**Message**](/docs/components/message), [**Bubble**](/docs/components/bubble), [**Attachment**](/docs/components/attachment), and [**Marker**](/docs/components/marker). This is the first phase of the chat components work. We're taking it one piece at a time, reimagining the abstraction behind each part, and shipping them as shadcn/ui components you can copy, compose, and adapt to your product. We are starting with the conversation layer: scrolling, message rows, bubbles, attachments, and markers. We asked ourselves: what makes a great streaming chat experience? Then we abstracted the core rules into a set of primitives: `MessageScroller`. ``` pnpm dlx shadcn@latest add message-scroller message bubble attachment marker ``` ## MessageScroller# `MessageScroller` is the scroll container for a conversation. It handles the parts that are easy to get wrong: anchored turns, streamed replies, saved thread restore, prepended history, jump-to-message, scroll controls, and visibility tracking. `MessageScroller` owns that behavior without owning your messages, AI state, transport, persistence, or model state. You bring the content renderer. The `MessageScroller` is also available as an unstyled headless component in `@shadcn/react`. ## Message, Bubble, Attachment, and Marker# The rest of the components cover the everyday pieces you need around the scroller. - `Message` lays out a row in the conversation with avatar, alignment, header, content, footer, and grouped messages. - `Bubble` renders the message surface, with variants, alignment, reactions, links, buttons, and collapsible content. - `Attachment` renders files and images with media, metadata, upload state, actions, and a full-card trigger that keeps actions separately clickable. - `Marker` renders status updates, system notes, bordered rows, and labeled separators for things like streaming state, tool activity, and date breaks. They are intentionally small. Compose them together for AI chats, support inboxes, team threads, group chats, and product-specific conversations. ## scroll-fade and shimmer# We also added two new CSS utilities for the details that make chat interfaces feel better. [`scroll-fade`](/docs/utils/scroll-fade) adds scroll-aware edge fades to scroll containers. Use it on `MessageScroller`, `ScrollArea`, attachment rows, and any long list where you want to hint at more content without adding overlays or scroll listeners. [`shimmer`](/docs/utils/shimmer) adds a text shimmer for live status. Use it for things like "Thinking…", "Generating response…", running tools, and streaming markers. Both utilities ship with `shadcn/tailwind.css`, so projects initialized with `npx shadcn@latest init` already have them. ## @shadcn/react# We also created `@shadcn/react`, a new package for unstyled, headless React components. The first primitive is `@shadcn/react/message-scroller`. The registry component wraps it with shadcn/ui styles, but the scroll behavior lives in the package: anchoring, auto-follow, prepend preservation, scroll commands, and visibility. This lets us ship behavior without locking it to a visual style. You still get copy-and-paste components that match your project, and the hard interaction logic stays tested in one place. Available now for Radix and Base UI. ## AI Elements# This does not replace [AI Elements](https://ai-sdk.dev/elements/overview). You can keep using AI Elements for AI interface components and patterns. This release is about bringing the core pieces of chat into shadcn/ui, one component at a time. If you are already using a component from AI Elements, you do not need to rewrite your app. Keep what works. Try the shadcn/ui version when you want the newer abstraction, the updated styling, or support across Radix and Base UI. The goal is to make these pieces easy to adopt independently. Replace one part, compose it with what you already have, and keep building.48:T99f,# June 2026 - GitHub Registries Turn any public GitHub repository into a shadcn registry. **You can now turn any public GitHub repository into a registry.** Add a `registry.json` file at the root of the repository, define the items you want to distribute, and users can install them directly from GitHub with the `shadcn` CLI. ``` pnpm dlx shadcn@latest add // ``` For example, to install the `project-conventions` item from the `acme/toolkit` repository: ``` pnpm dlx shadcn@latest add acme/toolkit/project-conventions ``` GitHub registries are source registries. You do not need to run `shadcn build`, publish generated item JSON files or set up a registry server. The CLI reads the root `registry.json`, resolves `include` entries, finds the requested item and installs the files declared by that item. ## Distribute anything Registry items are not limited to components. A GitHub registry can distribute components, hooks, utilities, design tokens, feature kits, project conventions, agent instructions, testing setup, CI workflows, release workflows, templates, codemods, migration kits and other project files. For example, a repository can expose a `project-conventions` item that installs shared docs, editor settings and agent instructions: ```json { "$schema": "https://ui.shadcn.com/schema/registry.json", "name": "acme-toolkit", "homepage": "https://github.com/acme/toolkit", "items": [ { "name": "project-conventions", "type": "registry:item", "files": [ { "path": "AGENTS.md", "type": "registry:file", "target": "~/AGENTS.md" }, { "path": ".editorconfig", "type": "registry:file", "target": "~/.editorconfig" }, { "path": "docs/conventions.md", "type": "registry:file", "target": "~/docs/conventions.md" } ] } ] } ``` ## Commands GitHub registry addresses work with the same commands as other registry addresses. List items from a GitHub registry: ``` pnpm dlx shadcn@latest list acme/toolkit ``` Search items: ``` pnpm dlx shadcn@latest search acme/toolkit --query conventions ``` View an item: ``` pnpm dlx shadcn@latest view acme/toolkit/project-conventions ``` Install an item: ``` pnpm dlx shadcn@latest add acme/toolkit/project-conventions ``` See the [GitHub Registries](/docs/registry/github) docs for the full guide.49:T6de,# May 2026 - shadcn eject Inline shadcn/tailwind.css and remove the shadcn dependency. When we added support for both Radix and Base UI, we needed a place for shared Tailwind utilities that both libraries depend on, e.g. custom variants like `data-open:` and `data-closed:` and utilities like `no-scrollbar`. We also ran into a few bugs while working on RTL support that were easier to fix in one shared place rather than duplicating across every component. So we created `shadcn/tailwind.css`. When you run `init`, it adds `@import "shadcn/tailwind.css"` to your global CSS file. It works just like other CSS imports such as `tw-animate-css`: a small dependency that is tree-shaken in production and resolved at build time. If you prefer not to depend on the `shadcn` package for that CSS, we've added the `shadcn eject` command. It inlines `shadcn/tailwind.css` into your global CSS file and removes the `shadcn` dependency from your project. ``` pnpm dlx shadcn@latest eject ``` **Before** ``` @import "tailwindcss"; @import "tw-animate-css"; @import "shadcn/tailwind.css"; ``` **After** ``` @import "tailwindcss"; @import "tw-animate-css"; /* ejected from shadcn@4.8.3 */ @theme inline { @keyframes accordion-down { from { height: 0; } to { height: var( --radix-accordion-content-height, var(--accordion-panel-height, auto) ); } } } @custom-variant data-open { &:where([data-state="open"]), &:where([data-open]:not([data-open="false"])) { @slot; } } ``` In a monorepo, run the command from the workspace that contains your `components.json` and global CSS file: ``` pnpm dlx shadcn@latest eject -c packages/ui ``` See the [CLI documentation](/docs/cli#eject) for more details.4a:T6db,# May 2026 - Introducing Rhea A more compact Luma. Smaller spacing. Denser surfaces. Built for focused product interfaces. Introducing Rhea, a new shadcn/ui style. A more compact Luma. Smaller spacing. Denser surfaces. Built for focused product interfaces. ![Rhea style preview](/_next/image?url=%2Fimages%2Frhea-light.png&w=3840&q=75&dpl=dpl_FoRVWZt8VvcLCsjK8K4FQanAhNWr)![Rhea style preview](/_next/image?url=%2Fimages%2Frhea-dark.png&w=3840&q=75&dpl=dpl_FoRVWZt8VvcLCsjK8K4FQanAhNWr) [Try Rhea in shadcn/create](/create?preset=b27GcrRo) Rhea started from a simple request we've heard a lot: Luma, but more compact. We looked at how people were using the new styles and what they were asking for, and the pattern was clear. A lot of teams wanted the softness and shape of Luma with tighter spacing, smaller controls, and more information density. Rhea keeps the same rounded foundation, but makes it more compact for product interfaces where space matters. Buttons, inputs, menus, cards, and lists all sit a little tighter so the UI can carry more without feeling crowded. ## Why a new style? We considered making this a spacing tweak for Luma, but `--spacing` is a multiplier. Changing it would change what familiar utilities mean across your app. `p-2`, `w-4`, and `m-16` would no longer mean the same size. That tradeoff felt wrong. Compactness should not force you to relearn Tailwind's spacing scale or wonder whether a utility means something different in one style than another. So Rhea is a new style instead. It lets us adjust component sizes, gaps, and density directly while keeping the underlying utility scale predictable. Available now in [shadcn/create](/create) for both Radix and Base UI. [Try Rhea](/create?preset=b27GcrRo)4b:Tbe1,# May 2026 - Registry Include and Validate Organize and validate source registries. This release adds two updates for registry authors: - `include` for composing large source registries from multiple `registry.json` files. - `shadcn registry validate` for checking source registries before publishing. This makes it easier to maintain source and dynamic registries without keeping one large `registry.json` file by hand. Registry authors can now organize a large source registry across multiple `registry.json` files and compose them with `shadcn build`. ``` registry.json components └── ui ├── button.tsx ├── input.tsx └── registry.json hooks ├── registry.json ├── use-media-query.ts └── use-toggle.ts ``` registry.json ```json { "$schema": "https://ui.shadcn.com/schema/registry.json", "name": "acme", "homepage": "https://acme.com", "include": [ "components/ui/registry.json", "hooks/registry.json" ] } ``` Included `registry.json` files are valid registry files for composition and may omit `name` and `homepage`. Only the root `registry.json` must define the registry metadata. components/ui/registry.json ```json { "$schema": "https://ui.shadcn.com/schema/registry.json", "items": [ { "name": "button", "type": "registry:ui", "files": [ { "path": "button.tsx", "type": "registry:ui" } ] } ] } ``` ## Build output `shadcn build` resolves included registries and writes a flattened `registry.json` without `include`. Item file paths are preserved from the root registry, so a file declared in `components/ui/registry.json` is written as `components/ui/button.tsx` in the built registry item. ## Validate your registry You can now validate a source registry before publishing or serving it. ``` pnpm dlx shadcn registry validate ``` Validation runs against the source registry files directly. You do not need to run `shadcn build` first. The command checks the root `registry.json`, included registry files, item schema errors, duplicate item names, include rules, and local item file paths. Validation reports all actionable errors it can find in one run. ## Registry loaders The `shadcn/registry` package also exports `loadRegistry` and `loadRegistryItem` for dynamic registry routes. app/r/registry.json/route.ts ```typescript import { loadRegistry } from "shadcn/registry" export async function GET() { const registry = await loadRegistry() return Response.json(registry) } ``` app/r/[name].json/route.ts ```typescript import { loadRegistryItem } from "shadcn/registry" export async function GET( _: Request, { params }: { params: Promise<{ name: string }> } ) { const { name } = await params const item = await loadRegistryItem(name) return Response.json(item) } ``` See the [registry.json documentation](/docs/registry/registry-json#include) and [getting started guide](/docs/registry/getting-started#structure-your-registry) for more details.4c:T67c,# May 2026 - Package Imports and Target Aliases Configure shadcn/ui with package.json imports and portable registry target aliases. We've added support for package imports and aliases in `files.target` in `shadcn@4.7.0`. ## Package imports# The `shadcn` CLI now supports `package.json#imports` for installing components, rewriting imports, and resolving third-party registries. You can use private `#...` import aliases from your `package.json` instead of relying only on `compilerOptions.paths` in `tsconfig.json`. package.json ```json { "imports": { "#components/*": "./src/components/*.tsx", "#lib/*": "./src/lib/*.ts", "#hooks/*": "./src/hooks/*.ts" } } ``` Then use the same roots in `components.json`: components.json ```json { "aliases": { "components": "#components", "ui": "#components/ui", "lib": "#lib", "hooks": "#hooks", "utils": "#lib/utils" } } ``` This also works in monorepos where app-local files use package imports and shared UI files are imported from workspace package exports. See the [package imports guide](/docs/package-imports) for setup details. ## Target aliases# Registry items can now use target aliases in `files[].target` to install files under the user's configured shadcn directories. For example, the following registry item will install the `prompt-input.tsx` file under the `ui/ai` directory. example.json ```json { "files": [ { "path": "registry/default/ai/prompt-input.tsx", "type": "registry:ui", "target": "@ui/ai/prompt-input.tsx" } ] } ``` See the [registry examples](/docs/registry/examples#target-placeholders) for more details.4d:Tbe6,# April 2026 - shadcn preset Decode, share, open, and resolve preset codes from the shadcn CLI. We added `shadcn preset` commands for working with preset codes. ## Decode a preset# You can decode a preset code to see exactly what it contains: pnpmnpmyarnbun ``` pnpm dlx shadcn@latest preset decode b5owWMfJ8l ``` Copy Copy`Preset code b5owWMfJ8l version b style mira baseColor mauve theme mauve chartColor amber iconLibrary hugeicons font inter fontHeading oxanium radius large menuAccent subtle menuColor inverted-translucent url https://ui.shadcn.com/create?preset=b5owWMfJ8l` ## Resolve from a project# Use `preset resolve` in an existing project to see the preset that matches your current configuration. pnpmnpmyarnbun ``` pnpm dlx shadcn@latest preset resolve ``` Copy Copy`Preset code b5Kc6P0Vc version b style luma baseColor olive theme lime chartColor sky iconLibrary hugeicons font geist fontHeading inherit radius default menuAccent subtle menuColor default url https://ui.shadcn.com/create?preset=b5Kc6P0Vc` It works with monorepos too: pnpmnpmyarnbun ``` pnpm dlx shadcn@latest preset resolve -c apps/web ``` Copy ## Share or open# Use `preset url` when you need a shareable link: pnpmnpmyarnbun ``` pnpm dlx shadcn@latest preset url b5owWMfJ8l ``` Copy Copy`https://ui.shadcn.com/create?preset=b5owWMfJ8l` Use `preset open` to open the preset on shadcn/create for customization: pnpmnpmyarnbun ``` pnpm dlx shadcn@latest preset open b5owWMfJ8l ``` Copy Copy`Opening https://ui.shadcn.com/create?preset=b5owWMfJ8l in your browser.` This makes presets easier to inspect, share, and hand off to coding agents without manually decoding codes or building URLs.4e:T82d,# April 2026 - Pointer Cursor Add cursor pointer behavior for buttons during project setup. You can now enable `cursor: pointer` for buttons when initializing a project. pnpmnpmyarnbun ``` pnpm dlx shadcn@latest init --pointer ``` Copy This adds the following CSS to your global CSS file: globals.css Copy`@layer base { button:not(:disabled), [role="button"]:not(:disabled) { cursor: pointer; } }` The `--pointer` option is not part of preset codes. It is applied as a project setup option, similar to `--rtl`.4f:T617,# April 2026 - Introducing Sera Minimal. Editorial. Typographic. Underline Controls and Uppercase Headings. Shaped by Print Design Principles. Introducing Sera, a new shadcn/ui style. Minimal. Editorial. Typographic. Underline Controls and Uppercase Headings. Shaped by Print Design Principles. ![Sera style preview](/_next/image?url=%2Fimages%2Fsera-01-light.png&w=3840&q=75&dpl=dpl_FoRVWZt8VvcLCsjK8K4FQanAhNWr)![Sera style preview](/_next/image?url=%2Fimages%2Fsera-01-dark.png&w=3840&q=75&dpl=dpl_FoRVWZt8VvcLCsjK8K4FQanAhNWr) Sera is a typography-first style built on print design principles. It pairs serif headings with sans-serif body text, uses square corners, uppercase tracking, and underlined controls to create an editorial feel for your app. Like the other new styles, Sera goes beyond theming. It changes the geometry, spacing, and feel of the components so your app starts from a different visual baseline. Available now in [shadcn/create](/create) for both Radix and Base UI. [Try Sera](/create?preset=b4xFeBLg4O) Deploy your shadcn/ui app on Vercel Trusted by OpenAI, Sonos, Adobe, and more. Vercel provides tools and infrastructure to deploy apps and features at scale. [Deploy to Vercel](https://vercel.com/new?utm_source=shadcn_site&utm_medium=web&utm_campaign=docs_cta_deploy_now_callout) Built by [shadcn](https://twitter.com/shadcn) at [Vercel](https://vercel.com/new?utm_source=shadcn_site&utm_medium=web&utm_campaign=docs_cta_deploy_now_callout). The source code is available on [GitHub](https://github.com/shadcn-ui/ui).3e:["$","$L3f",null,{"orgSlug":"shadcn","initialReleases":[{"id":"rel_WHfs7pzXp05Yc9KbyPU34","version":null,"title":"August 2026 - Private GitHub Registries","summary":"Registry items can now be installed from private GitHub repositories. If logged in to the GitHub CLI, setup is zero-config; otherwise set GH_TOKEN or GITHUB_TOKEN, with a fine-grained token scoped to Contents: Read-only recommended. Works with the add, list, search, view, and registry validate commands.","content":"$40","publishedAt":"2026-08-24T00:00:00.000Z","fetchedAt":"2026-08-24T11:33:35.170Z","url":"https://ui.shadcn.com/docs/changelog/2026-08-private-github-registries","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui now installs registry items from private GitHub repos","titleShort":"Private GitHub repos now installable via registry CLI","breaking":"none","importance":3,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Registry items can now be installed from private GitHub repositories. If logged in to the GitHub CLI, setup is zero-config; otherwise set GH_TOKEN or GITHUB_TOKEN, with a fine-grained token scoped to Contents: Read-only recommended. Works with the add, list, search, view, and registry validate commands.

"},{"id":"rel_CID-ieWV24SHiSTBOy7nk","version":null,"title":"August 2026 - Human in the Loop","summary":"@shadcn/helpers can now mock human-in-the-loop flows for the AI SDK, pausing for real user input, waiting for approvals, and continuing with the user's decision. Everything streams through the real useChat lifecycle, so tool cards, approval prompts, and question flows behave as in production.","content":"$41","publishedAt":"2026-08-12T00:00:00.000Z","fetchedAt":"2026-08-11T21:49:58.605Z","url":"https://ui.shadcn.com/docs/changelog/2026-08-helpers-human-in-the-loop","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui adds human-in-the-loop mocking for AI SDK flows","titleShort":"AI SDK flows now mock approvals and pauses","breaking":"none","importance":3,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

@shadcn/helpers can now mock human-in-the-loop flows for the AI SDK, pausing for real user input, waiting for approvals, and continuing with the user's decision. Everything streams through the real useChat lifecycle, so tool cards, approval prompts, and question flows behave as in production.

"},{"id":"rel_iiB3nxqrXki0SsUZ-wbAq","version":null,"title":"August 2026 - Questionnaire","summary":"","content":"$42","publishedAt":"2026-08-05T00:00:00.000Z","fetchedAt":"2026-08-05T23:07:36.250Z","url":"https://ui.shadcn.com/docs/changelog/2026-08-questionnaire","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

A new component for building multi-step question flows with fixed, freeform, multiple, and skippable answers.

"},{"id":"rel_rqMucoHBSPWewSfiM-QNu","version":null,"title":"July 2026 - Dynamic Search","summary":"When running `shadcn search`, the CLI forwards search parameters to your registry as query params, making search fast for large registries by no longer requiring the full catalog download. Dynamic search is opt-in and static registries continue working without changes.","content":"# July 2026 - Dynamic Search\n\nRegistries can now handle search server-side.\n\n**Registries can now handle search server-side.**\n\nWhen you run `shadcn search`, the CLI forwards the search parameters to your registry as query params:\n\n`GET /r/registry.json?q=button&limit=50&offset=0`\n\nReturn the matching items with a `pagination` object and the CLI uses your results as-is. This makes search fast for large registries: no more downloading the full catalog to search it.\n\nregistry.json?q=button&limit=1\n\n```json\n{\n \"name\": \"acme\",\n \"homepage\": \"https://acme.com\",\n \"items\": [\n {\n \"name\": \"button\",\n \"type\": \"registry:ui\",\n \"description\": \"A button component.\"\n }\n ],\n \"pagination\": {\n \"total\": 12,\n \"offset\": 0,\n \"limit\": 1,\n \"hasMore\": true\n }\n}\n```\n\nDynamic search is opt-in. Static registries ignore the query params and keep working without any changes.\n\nSee the [Dynamic Search](/docs/registry/dynamic-search) docs for the full guide.","publishedAt":"2026-07-31T00:00:00.000Z","fetchedAt":"2026-07-31T16:44:12.368Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-dynamic-search","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui July 2026 adds server-side search for registries","titleShort":"Registries can now handle search server-side","breaking":"none","importance":2,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

When running shadcn search, the CLI forwards search parameters to your registry as query params, making search fast for large registries by no longer requiring the full catalog download. Dynamic search is opt-in and static registries continue working without changes.

"},{"id":"rel_n4a5Np2oj1BFrKBRDMcBT","version":null,"title":"July 2026 - Toast","summary":"New Toast component built on Base UI primitives.","content":"A new Toast component built on Base UI primitives.","publishedAt":"2026-07-23T00:00:00.000Z","fetchedAt":"2026-07-23T17:07:02.239Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-toast","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui July 2026 adds Toast component built on Base UI primitives","titleShort":"Toast component ships on Base UI primitives","breaking":"none","importance":3,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

New Toast component built on Base UI primitives.

"},{"id":"rel_GGCVWR1A116BAaVH9HizY","version":null,"title":"July 2026 - React Aria","summary":"React Aria Components are now available as a first-class component base alongside Base UI and Radix. Developers can choose it in shadcn/create or initialize projects with `--base aria`, with CLI handling dependencies, registry resolution, styles, and component installation across all eight styles.","content":"$43","publishedAt":"2026-07-17T00:00:00.000Z","fetchedAt":"2026-07-17T18:25:58.367Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-react-aria","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui adds React Aria as a first-class component base","titleShort":"React Aria now a first-class component base","breaking":"none","importance":4,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

React Aria Components are now available as a first-class component base alongside Base UI and Radix. Developers can choose it in shadcn/create or initialize projects with --base aria, with CLI handling dependencies, registry resolution, styles, and component installation across all eight styles.

"},{"id":"rel_gn1LFHRUlDF3D1svmxJl-","version":null,"title":"July 2026 - Introducing @shadcn/helpers","summary":"A new open source @shadcn/helpers package provides adapters for AI SDK and TanStack AI that let you write conversations in code and run them through useChat without a model, API route, or network request.","content":"$44","publishedAt":"2026-07-14T00:00:00.000Z","fetchedAt":"2026-07-14T16:57:10.654Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-helpers","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui introduces @shadcn/helpers for AI SDK and TanStack AI chat testing","titleShort":"@shadcn/helpers package lets you write chat conversations in code","breaking":"none","importance":3,"composition":{"bugs":0,"enhancements":0,"features":2},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

A new open source @shadcn/helpers package provides adapters for AI SDK and TanStack AI that let you write conversations in code and run them through useChat without a model, API route, or network request.

"},{"id":"rel_KyhJ3eP4gifngz4OuMzTP","version":null,"title":"July 2026 - Introducing shadcn/typeset","summary":"shadcn/typeset is a new styling system for HTML and rendered markdown delivered as a single CSS file. Add the \"typeset\" class to style headings, paragraphs, lists, tables, and code, with CSS custom properties for size, leading, and flow per context.","content":"$45","publishedAt":"2026-07-10T00:00:00.000Z","fetchedAt":"2026-07-10T19:11:15.367Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-typeset","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui introduces shadcn/typeset, a complete typography system for HTML","titleShort":"shadcn/typeset: one CSS file for all HTML typography","breaking":"none","importance":3,"composition":{"bugs":0,"enhancements":0,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

shadcn/typeset is a new styling system for HTML and rendered markdown delivered as a single CSS file. Add the \"typeset\" class to style headings, paragraphs, lists, tables, and code, with CSS custom properties for size, leading, and flow per context.

"},{"id":"rel_TUxVOyVHeyyTBGlCTm6n4","version":null,"title":"July 2026 - Base UI as the Default","summary":"New projects created with shadcn/ui now default to Base UI instead of Radix, though Radix remains fully supported and mature projects on it do not need to migrate. A migration skill allows progressive component-by-component migration via coding agents, with per-component reporting and rollback via git branches.","content":"$46","publishedAt":"2026-07-02T00:00:00.000Z","fetchedAt":"2026-07-03T15:57:18.350Z","url":"https://ui.shadcn.com/docs/changelog/2026-07-base-ui-default","media":[],"type":"feature","prerelease":false,"titleGenerated":"shadcn/ui defaults to Base UI; Radix still fully supported","titleShort":"Base UI is now the default; Radix stays supported","breaking":"major","importance":3,"composition":{"bugs":0,"enhancements":1,"features":1},"source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

New projects created with shadcn/ui now default to Base UI instead of Radix, though Radix remains fully supported and mature projects on it do not need to migrate. A migration skill allows progressive component-by-component migration via coding agents, with per-component reporting and rollback via git branches.

"},{"id":"rel_WYna2z1l_2GFHAXiPxnTn","version":null,"title":"June 2026 - Components for Chat Interfaces","summary":"","content":"$47","publishedAt":"2026-06-26T00:00:00.000Z","fetchedAt":"2026-06-26T20:05:22.098Z","url":"https://ui.shadcn.com/docs/changelog/2026-06-chat-components","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

MessageScroller, Message, Bubble, Attachment, and Marker. Components for building chat interfaces.

"},{"id":"rel_PgdPqjOMMDHCRM293wZzD","version":null,"title":"June 2026 - GitHub Registries","summary":"","content":"$48","publishedAt":"2026-06-01T00:00:00.000Z","fetchedAt":"2026-06-01T15:05:36.831Z","url":"https://ui.shadcn.com/docs/changelog/2026-06-github-registries","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Turn any public GitHub repository into a shadcn registry.

"},{"id":"rel_yF7EnMDNNXjmy-cejv1Xq","version":null,"title":"May 2026 - shadcn eject","summary":"","content":"$49","publishedAt":"2026-05-31T00:00:00.000Z","fetchedAt":"2026-05-31T14:05:28.790Z","url":"https://ui.shadcn.com/docs/changelog/2026-05-shadcn-eject","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Inline shadcn/tailwind.css and remove the shadcn dependency.

"},{"id":"rel_aX4Z0UCPuIrl9sUKStD5n","version":null,"title":"May 2026 - Introducing Rhea","summary":"","content":"$4a","publishedAt":"2026-05-26T00:00:00.000Z","fetchedAt":"2026-05-26T19:05:19.737Z","url":"https://ui.shadcn.com/docs/changelog/2026-05-rhea","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

A more compact Luma. Smaller spacing. Denser surfaces. Built for focused product interfaces.

"},{"id":"rel_lMs2JZ73sQofIYlCPwiQk","version":null,"title":"May 2026 - Registry Include and Validate","summary":"","content":"$4b","publishedAt":"2026-05-20T00:00:00.000Z","fetchedAt":"2026-05-21T14:05:39.917Z","url":"https://ui.shadcn.com/docs/changelog/2026-05-registry-include","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Organize and validate source registries.

"},{"id":"rel_Ud2KlN4SXCAJ0HKhSXa0I","version":null,"title":"May 2026 - Package Imports and Target Aliases","summary":"","content":"$4c","publishedAt":"2026-05-05T00:00:00.000Z","fetchedAt":"2026-05-05T17:01:10.953Z","url":"https://ui.shadcn.com/docs/changelog/2026-05-package-imports-target-aliases","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Configure shadcn/ui with package.json imports and portable registry target aliases.

"},{"id":"rel_z5OeT1BCnBabefqr8gako","version":null,"title":"April 2026 - shadcn preset","summary":"","content":"$4d","publishedAt":"2026-04-28T00:00:00.000Z","fetchedAt":"2026-04-28T18:00:45.952Z","url":"https://ui.shadcn.com/docs/changelog/2026-04-preset-commands","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Decode, share, open, and resolve preset codes from the shadcn CLI.

"},{"id":"rel_XXl3x0xCt2z_yO_GaZtQb","version":null,"title":"April 2026 - Pointer Cursor","summary":"","content":"$4e","publishedAt":"2026-04-25T00:00:00.000Z","fetchedAt":"2026-04-25T12:00:53.986Z","url":"https://ui.shadcn.com/docs/changelog/2026-04-pointer-cursor","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Add cursor pointer behavior for buttons during project setup.

"},{"id":"rel_fbVckXlXgb1mqsGQ_fiZB","version":null,"title":"April 2026 - Partial Preset Apply","summary":"","content":"# April 2026 - Partial Preset Apply\n\nApply only the theme or fonts from a preset while keeping your existing components.\n\nYou can now selectively apply a preset.\n\nSay someone shares a preset with you and you already have your own components, but you like the theme or the fonts. Now you can apply just that.\n\nKeep your components. Apply only what you want.\n\n```bash\n# Apply the full preset.\nnpx shadcn@latest apply --preset b2D0vQ7G4\n\n# Apply only the theme.\nnpx shadcn@latest apply --preset b2D0vQ7G4 --only theme\n\n# Apply only the fonts.\nnpx shadcn@latest apply --preset b2D0vQ7G4 --only font\n\n# Apply theme and fonts.\nnpx shadcn@latest apply --preset b2D0vQ7G4 --only theme,font\n```\n\nThe default behavior is unchanged. Running `shadcn apply --preset ` still applies the full preset.\n\nPartial preset apply currently supports `theme` and `font`.","publishedAt":"2026-04-22T00:00:00.000Z","fetchedAt":"2026-04-23T11:00:16.309Z","url":"https://ui.shadcn.com/docs/changelog/2026-04-partial-preset-apply","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Apply only the theme or fonts from a preset while keeping your existing components.

"},{"id":"rel_tsVPEDympTGTDMtPuwMvU","version":null,"title":"April 2026 - Introducing Sera","summary":"","content":"$4f","publishedAt":"2026-04-16T00:00:00.000Z","fetchedAt":"2026-04-16T20:03:30.811Z","url":"https://ui.shadcn.com/docs/changelog/2026-04-sera","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Minimal. Editorial. Typographic. Underline Controls and Uppercase Headings. Shaped by Print Design Principles.

"},{"id":"rel_i8uhrWFO70gBTq5Gt6BSH","version":null,"title":"April 2026 - shadcn apply","summary":"","content":"# April 2026 - shadcn apply\n\nCopy Page\n\nSwitch presets in existing projects without starting over.\n\nWe added `shadcn apply` so you can switch presets in an existing project without starting over.\n\nWhen you run `npx shadcn@latest apply` in an existing project, we apply a new preset, reinstall your existing components, and update your theme, colors, CSS variables, fonts, and icons.\n\npnpmnpmyarnbun\n\n```\npnpm dlx shadcn@latest apply --preset b2D0vQ7G4\n```\n\nCopy\n\nThe CLI keeps the current base and RTL settings from your existing project, even when the preset URL was generated with different values.\n\n[\n\nTry a Preset\n\n](/create)","publishedAt":"2026-04-08T00:00:00.000Z","fetchedAt":"2026-04-08T14:02:54.767Z","url":"https://ui.shadcn.com/docs/changelog/2026-04-shadcn-apply","media":[],"type":"feature","prerelease":false,"titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":"$undefined","composition":"$undefined","source":{"slug":"shadcn-ui","name":"shadcn/ui","type":"feed","appStore":"$undefined","video":"$undefined"},"product":null,"bodyHtml":"

Copy Page

"}],"initialCursor":"2026-04-08T00:00:00.000Z|2026-04-08T14:02:54.767Z|rel_i8uhrWFO70gBTq5Gt6BSH","multipleSourcesExist":false,"availableSourceTypes":["feed"],"orgAvatarUrl":"https://media.releases.sh/orgs/shadcn.png","productLinks":"$L50"}]