Configuration

Everything the CLI needs to know about your project lives in a single lerpa.json file at the root, generated by init. You can edit it by hand at any time.

lerpa.json

{
  "style": "default",
  "tailwind": {
    "config": "tailwind.config.ts",
    "css": "src/app/globals.css"
  },
  "aliases": {
    "components": "@/components",
    "utils": "@/lib/utils"
  },
  "packageManager": "pnpm"
}

Fields

style

The component style preset. Currently "default".

tailwind.config

Path to your Tailwind config file (e.g. tailwind.config.ts).

tailwind.css

Path to your global stylesheet that imports Tailwind and holds the design tokens — the CLI's theme command writes here.

aliases.components

Import alias / target folder for components (default @/components). UI lands in <alias>/ui, blocks in <alias>/blocks.

aliases.utils

Import alias for helper utilities such as cn (default @/lib/utils).

packageManager

One of pnpm, npm, yarn, or bun — used when the CLI installs npm dependencies a component requires.

How the CLI resolves it

On every add, the CLI reads lerpa.jsonfrom your current working directory, rewrites a component's internal import paths to match your aliases (for example @/lib/cn → @/lib/utils), writes the file into your components folder, and installs any required npm dependencies with your chosen package manager. If lerpa.json is missing, the CLI asks you to run init first.

Verify your configuration anytime with the diagnostics command: