CLI

The CLI copies source files into your project — like shadcn/ui. Nothing is installed from npm at runtime except the few peer packages a component needs.

init

Creates components.json and the @/ alias in the Expo app you're in. Detects src/ or root layouts.

init my-app

Starts a new Expo app in ./my-app (create-expo-app) and sets ExpoKit up inside it.

add

Copies an item and its registry dependencies, then installs missing packages.

list

Every component, block and template in the registry.

update

Refreshes template framework files after an upgrade; your tabs.ts is kept.

doctor

Checks components.json, package.json main, routes and peer dependencies.

Saves a CLI token (create one on your Account page) so add can download Pro items. logout removes it; whoami shows your plan.

Items marked PRO in add --list are downloaded from expokit.karandev.in instead of being bundled. Create a token on your /account page, run login once, then add them like any other item. The token is stored in ~/.expo-kit/credentials.json (or set EXPO_KIT_TOKEN in CI).

Shared files

Components share src/lib/kit.tsx (and sometimes each other, e.g. Password Input uses Floating Input). The CLI writes a shared file only if it is missing or unchanged — if you edited it, it is kept and the CLI tells you. Pass --force to replace it.

Paths come from components.json: paths.components, paths.lib, paths.app. Change them before adding items if your project uses a different layout.

NextBrowse components

Did you like the content?