@soralabsoss/sora-cli

A CLI for installing components from any shadcn-compatible registry into your project — defaults to Sora UI and other Sora Labs products, but works against any registry via --registry <url>.

Usage

npx @soralabsoss/sora-cli add text-effect

# multiple components
npx @soralabsoss/sora-cli add text-effect draw-underline-link

# interactive picker
npx @soralabsoss/sora-cli add

# list available components
npx @soralabsoss/sora-cli list

# compare installed components against the registry
npx @soralabsoss/sora-cli diff text-effect

Options

npx @soralabsoss/sora-cli add text-effect --path src/components/ui
npx @soralabsoss/sora-cli add card --cwd packages/ui       # run as if started in packages/ui (monorepos)
npx @soralabsoss/sora-cli add text-effect --force
npx @soralabsoss/sora-cli add text-effect --registry ui                          # default; other Sora Labs products register here later
npx @soralabsoss/sora-cli add some-item --registry https://any-shadcn-registry.com   # or point at any shadcn-compatible registry directly
npx @soralabsoss/sora-cli add text-effect --yes           # skip the install confirmation, for scripts/CI
npx @soralabsoss/sora-cli add text-effect --dry-run       # preview what would change, write nothing
npx @soralabsoss/sora-cli add text-effect --silent        # only print summary lines, not per-file output
npx @soralabsoss/sora-cli add text-effect --view          # print file contents instead of writing them
npx @soralabsoss/sora-cli --version

How it works

The CLI fetches a shadcn-compatible registry (<product-url>/r/registry.json, <product-url>/r/<name>.json) built by that product's own registry:build step, resolves the dependency tree, writes files into your project, and installs npm dependencies with your detected package manager (bun/pnpm/yarn/npm).

Each Sora Labs product registers its base URL in src/constants.ts as a short --registry key — adding a new product only requires adding an entry there, no other logic changes. --registry also accepts a full URL directly, so it works against any shadcn-compatible registry, not just Sora Labs' own — it must be HTTPS (plain HTTP is only allowed for localhost/127.0.0.1, for local registry development). Registry content isn't cryptographically signed, so only point --registry at a registry you trust — it's written into your project and its dependency list is fed straight into your package manager.

Since components are copied into your project rather than installed as a package, sora diff is the way to check whether the registry has changed a component since you installed it — it reports differences without writing anything; re-run add <component> --force --yes to apply an update.

In a monorepo, --cwd <path> (or -c) runs add/diff as if the CLI had been started inside <path> — it picks up that workspace's own tsconfig.json/components.json aliases and writes components there, without you having to cd into it first. --path is different: it only overrides where files get written, without changing which config gets detected.

Every command also does a quick, non-blocking check against npm for a newer published version (printed to stderr, never mixed into --json output). Set SORA_NO_UPDATE_CHECK=1 to disable it, e.g. in CI.

Development

bun install
bun run build      # bundles src/index.ts -> dist/index.js via tsup
bun run typecheck
bun test           # run test suite
node dist/index.js list