Skip to content

Installation

Pro components ship through a private shadcn registry. Register it once, set your token, and install any component straight into your app.

Get your token

Your EASEUI_PRO_TOKEN arrives by email when you purchase a plan, tied to your license. It never expires while your plan is active, and only its hash is stored on our side.

Choose a plan

Register the registry

Add the @easeui-pro registry to your project's components.json, beside the free public @easeui registry that Pro components build on.

components.json
{
  "registries": {
    "@easeui": "https://easeui.dev/r/{name}.json",
    "@easeui-pro": {
      "url": "https://pro.easeui.dev/r/{name}.json",
      "headers": {
        "Authorization": "Bearer ${EASEUI_PRO_TOKEN}"
      }
    }
  }
}

Set your token

The registry reads your token from the EASEUI_PRO_TOKEN environment variable. Export it, or prefix a single command with it.

terminal
# Set it once for your shell session
export EASEUI_PRO_TOKEN="eui_pro_live_xxxxxxxxxxxx"

# ...or pass it inline for a single install
EASEUI_PRO_TOKEN="eui_pro_live_xxxxxxxxxxxx" npx shadcn@latest add @easeui-pro/cards

Install a component

Run the CLI with the namespaced slug, or point it at the authenticated URL directly if you'd rather not touch components.json. Every component page lists its own command.

terminal
# Namespaced slug, once the registry is registered
bunx --bun shadcn add @easeui-pro/cards

# Direct registry URL, if you'd rather not touch components.json
npx shadcn@latest add https://pro.easeui.dev/r/cards.json

Manual install

Want the raw source instead of the CLI? Fetch the registry item with your token. The JSON response carries every file's contents, its dependencies, and the target paths, so you copy them into your project by hand.

terminal
curl -H "Authorization: Bearer $EASEUI_PRO_TOKEN" \
  https://pro.easeui.dev/r/cards.json

The response's files array maps each source file to its destination, and registryDependencies lists the public @easeui primitives it relies on.

Need a hand? Browse the component library for what's built and what's next, or see the agent guide if a coding agent is doing the install.