components.json

Configure the Oros registry, source paths, and import aliases for your app.

App configuration

Start with this base-nova configuration, then update the CSS and alias paths to match your app.

{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "base-nova",
  "rsc": true,
  "tsx": true,
  "tailwind": {
    "config": "",
    "css": "app/globals.css",
    "baseColor": "neutral",
    "cssVariables": true,
    "prefix": ""
  },
  "iconLibrary": "lucide",
  "rtl": false,
  "aliases": {
    "components": "@/components",
    "utils": "@/lib/utils",
    "ui": "@/components/ui",
    "lib": "@/lib",
    "hooks": "@/hooks"
  },
  "menuColor": "default",
  "menuAccent": "subtle",
  "registries": {
    "@oros": "https://ui.oros.markets/r/{name}.json"
  }
}

Registry namespace

The @oros key maps CLI names such as @oros/button to component metadata served by the Oros production registry.

Import aliases

The CLI rewrites registry imports to @/components/ui, @/lib, and @/hooks according to this file. Keep these aliases aligned with the folder structure in your app.