Support for Adding Components via Local registry.json File

[Prathamesh-chougale-17]

🧩 Feature Request: Support for Local registry.json in CLI

The shadcn CLI currently depends on a remote registry for fetching component definitions. This limitation restricts usage in air-gapped, offline, or enterprise environments where internet access is limited or controlled. Adding support for a local registry.json file would address this gap and make the tool more versatile.

---

Why this matters

• Offline-first development: Developers working without continuous internet access—such as on planes, remote locations, or secure networks—cannot currently use the CLI.

• Enterprise and internal tooling: Many companies use private design systems and cannot expose their component registry over the internet. A local file-based approach enables internal teams to build with shadcn-ui without compromising on security or setup simplicity.

• Custom component libraries: This feature would allow teams to define and share custom components via local registries, promoting better collaboration without relying on external infrastructure.

• Improved portability: Projects could bundle a registry.json with the codebase, ensuring consistent component scaffolding across machines and developers.

• Reduced dependency on remote resources: Allowing local file support minimizes risk in scenarios where external endpoints are unavailable or deprecated in the future.

---

Suggested behavior

Introduce a flag to the CLI such as:

npx shadcn@latest add --registry ./registry.json

This would parse the given local file instead of fetching from the remote registry.

---

Implementing this would improve adoption, enhance flexibility, and support modern workflows that prioritize autonomy, speed, and privacy.

---