sigma-ui.config.json

Configuration for your project.

The sigma-ui.config.json config file is created during initialization. It holds SIGMA-UI configuration for your project.

You can create a sigma-ui.config.json file in your project by running the following command:

bash
npx sigma-ui init

See the CLI section for more information.

$schema ​

You can see the JSON Schema for sigma-ui.config.json here.

json
{
  "$schema": "https://sigma-ui.dev/schema.json"
}

Config options ​

styleSystem ​

This field determines the style system for the components (CSS or Tailwind).

json
{
  "styleSystem": "tailwind" | "css"
}

Try changing the style system and see how it affects the component's code:

Preview:

cssPath ​

Stylesheet that holds the theme variables. For Tailwind this file imports tailwindcss and tw-animate-css.

json
{
  "cssPath": "src/assets/index.css"
}

baseColor ​

Theme base color used to generate the palette.

json
{
  "baseColor": "grayscale"
}

Changing baseColor after initialization does not rewrite components that are already in the project. Run init again and re-add the components to pick up a new palette.

tailwind ​

Skip this section if you are not using the Tailwind style system.

tailwind.config ​

Optional path to a legacy tailwind.config.js. Leave it empty for CSS-first Tailwind v4. When it is set, the stylesheet references that file with @config.

json
{
  "tailwind": {
    "config": ""
  }
}

aliases ​

The CLI uses these values and the paths config from your tsconfig.json file to place generated components in the correct location.

Path aliases have to be set up in your tsconfig.json file. It will fallback to tsconfig.app.json if no paths were found in tsconfig.json

aliases.utils ​

Import alias for your utility functions.

json
{
  "aliases": {
    "utils": "@ui/utils"
  }
}

aliases.components ​

Path to where CLI will add components.

json
{
  "aliases": {
    "components": "@/components"
  }
}
Edit this page on GitHub