185 Pro components and page blocks

Get Pro
All guides

Install components from any shadcn registry

The shadcn CLI installs from any registry, not only shadcn/ui. Here is how to point it at one, by URL or by namespace.

Updated

What a registry is

A shadcn registry is a set of JSON files. Each item lists its source files, the npm packages it needs and any other registry items it builds on. The shadcn CLI reads the item, installs the packages and writes the source into your project, where you own and edit it.

shadcn/ui is one registry. Anyone can publish another, and the same CLI installs from all of them. A registry usually has an index at /r/registry.json listing every item.

Install from a URL

The quickest way: pass the item's URL. It needs nothing beyond a project set up with shadcn init.

Terminal
npx shadcn@latest add https://uibrik.com/r/tag-input.json

Dependencies come along. If the item needs a shadcn/ui component or another item from its registry, the CLI installs that too.

Use a namespace

For a registry you use often, add a namespace. It maps a name starting with @ to a URL pattern with a {name} placeholder.

components.json
{
  "registries": {
    "@uibrik": "https://uibrik.com/r/{name}.json"
  }
}
Terminal
npx shadcn@latest add @uibrik/tag-input @uibrik/scramble-text

You can also add it from the terminal with npx shadcn@latest registry add @uibrik=https://uibrik.com/r/{name}.json. Registries listed in shadcn's own directory are found by name without any set-up. Namespaces also feed the shadcn MCP server, so your AI assistant can browse them.

Private registries

A registry entry can be an object with headers. Values written as ${VAR_NAME} are read from your environment, so the key never lands in the file you commit.

components.json
{
  "registries": {
    "@uibrik-pro": {
      "url": "https://uibrik.com/r/pro/{name}.json",
      "headers": { "Authorization": "Bearer ${UIBRIK_LICENSE}" }
    }
  }
}
.env.local
UIBRIK_LICENSE=your-license-key

This is how paid component libraries ship through the CLI. The uibrik Pro docs walk through it end to end.

Find registries

After install

Where files go

Each registry picks a folder. uibrik writes to components/uibrik/<name>/, so its files never collide with shadcn/ui's in components/ui/.

Updating

Run the same add command again. The CLI asks before it overwrites existing files, so commit your changes first and review the diff after.

Questions

What is a shadcn registry?
A set of JSON files that describe components: their source files, npm dependencies and other registry items they need. The shadcn CLI reads them and writes the source into your project.
How do I install a component from a registry URL?
Pass the item's JSON URL to the CLI: npx shadcn@latest add https://uibrik.com/r/tag-input.json. No set-up beyond shadcn init is needed.
How do I add a registry namespace?
Add it under registries in components.json, mapping a name that starts with @ to a URL with a {name} placeholder. Then install with npx shadcn@latest add @namespace/component.
Can a shadcn registry be private?
Yes. A registry entry can send headers, and values written as ${VAR_NAME} are read from your environment, so a license key or token stays out of the file.

More guides