components.json file holds configuration for your project.
We use it to understand how your project is set up and how to generate components customized for your project.
The
components.json file is optional and only required if you’re using the CLI to add components to your project. If you’re using the copy and paste method, you don’t need this file.components.json file in your project by running the following command:
$schema
You can see the JSON Schema forcomponents.json here.
components.json
tailwind
Configuration to help the CLI understand how Tailwind CSS is set up in your project. See the installation section for how to set up Tailwind CSS.tailwind.css
Path to the CSS file that imports Tailwind CSS into your project.components.json
tailwind.baseColor
This is used to generate the default color palette for your components. This cannot be changed after initialization.components.json
aliases
The CLI uses these values and thealias config from your svelte.config.js file to place generated components in the correct location.
Path aliases have to be set up in your svelte.config.js file.
aliases.lib
Import alias for your library, which is typically where you store your components, utils, hooks, etc.components.json
aliases.utils
Import alias for your utility functions.components.json
aliases.components
Import alias for your components.components.json
aliases.ui
Import alias for your UI components.components.json
aliases.hooks
Import alias for your hooks, which in Svelte 5 are reactive functions/classes whose files typically end in.svelte.ts or .svelte.js.
components.json
Typescript
Typescript can be enabled or disabled.components.json
tsconfig.json or jsconfig.json, or if it is located in a different directory:
components.json
Registry
The registry URL tells the CLI where to fetch the shadcn-svelte components/registry from. You can pin this to a specific preview release or your own fork of the registry.components.json