mnui-cli

Set up @mnui components in an Expo project. A thin wrapper over the shadcn CLI — it writes the config shadcn can't (metro, tsconfig, the global.css import), then delegates installs to shadcn add.

Usage

# one-time setup in your Expo app
npx mnui-cli init

# add components (dependencies resolve automatically)
npx mnui-cli add button badge pill-tabs

mnui init

Writes/patches, idempotently:

• components.json — the @mnui registry + aliases.
• tsconfig.json — baseUrl: "." + paths { "@/*": ["./src/*"] } (so @/ resolves).
• metro.config.js — wraps withUniwindConfig (or prints the change if the file already exists).
• app entry _layout — prepends import "./…/global.css".

Then runs shadcn add @mnui/mnui-base (installs uniwind/tailwindcss/cva/… + the theme + cn/motion).

Flags: --skip-base writes only the config, skipping the base install.

mnui add <name…>

Passthrough to shadcn add @mnui/<name>.

Zero dependencies

Node built-ins + the shadcn CLI via npx. Assumes the standard Expo Router layout (src/app/_layout.tsx, src/global.css); for other layouts, run the manual steps in docs/registry/01-consuming.md.

Publishing

npx mnui-cli requires this package on npm. After npm login, from packages/cli: npm publish (unscoped names are public by default — no --access public, no org needed). (Until published, run it locally: node packages/cli/bin/index.mjs init.)