Capítulo 105 de 108
An opt-in, official directory of open-source registries; being listed lets users add your namespace (@acme) by name instead of pasting a full URL template. Not required to use owner/repo/item GitHub addressing.
shadcn add/shadcn search, adding matches to components.json automatically. Full list at https://ui.shadcn.com/r/registries.json./registry.json and /component-name.json files live at the registry root.content in files: For directory submission, the files array (if present) must NOT include a content property (content is fetched separately).{
"$schema": "https://ui.shadcn.com/schema/registry.json",
"name": "acme",
"homepage": "https://acme.com",
"items": [
{ "name": "login-form", "type": "registry:component", "title": "Login Form", "description": "A login form component.", "files": [{ "path": "registry/new-york/auth/login-form.tsx", "type": "registry:component" }] }
]
}
content inline.| Requirement | Detail |
|---|---|
| Open source | must be publicly accessible |
| Valid schema | conforms to registry-json spec |
| Flat structure | no nested item files |
No content in files | content fetched separately |
include-based registry directly: the directory requires flat structure; resolve/flatten via shadcn build before submission if needed.owner/repo/item addresses work without any submission — the directory is only for @namespace shortcuts.apps/v4/registry/directory.json in the shadcn-ui/ui repo → run pnpm validate:registries → open a PR.@acme instead of full URL); it changes nothing about how the registry itself must be built.