shadcn-core-registry

To configure a custom shadcn registry, define the `registries` entry in components.json using a URL template that includes the required `{name}` placeholder. This template allows the CLI to resolve namespaces into validated registry items and write files to the proper aliases.

shadcn UI installation failures often stem from incorrect components.json configuration, such as missing the `{name}` placeholder in URL templates, improper alias mapping, or immutable field conflicts. Template placeholders and env-var expansion must be strictly enforced to resolve namespaces correctly.

Use `${ENV_VAR}` interpolation within the `headers` and `params` fields of your components.json registry configuration. This environment variable expansion avoids committing secrets directly to source control while enabling secure, production-ready access to private or paid registries.

Yes, the shadcn registry format supports both Tailwind v3 and v4, but you must ensure `style`, `tailwind.baseColor`, and `tailwind.cssVariables` are correctly aligned before running init. Token mismatches between versions are a common source of install failures.

Hosting your own shadcn registry requires generating public `r/*.json` files that adhere to the registry item type and file target schemas. You must enforce proper content negotiation expectations and use correct `{name}` placeholder usage within your immutable style and theme token generation.

Fields determining style and theme token generation, specifically `style`, `tailwind.baseColor`, and `tailwind.cssVariables`, are immutable after initialization. Modifying these decision constraints post-init causes registry resolution errors and inconsistent component installation behavior.