Skip to main content
Helios provides a suite of commands for discovering, installing, and managing components from the component registry.

Overview

The component management commands allow you to:
  • Browse available components in the registry
  • Add components to your project
  • List installed components
  • Update components to the latest version
  • Remove components you no longer need
  • Diff local changes against registry versions

helios components

List and search available components in the registry.

Usage

Arguments

string
Search query to filter components by name or description.

Options

string
Filter by framework: react, vue, svelte, solid, or vanilla. Short form: -f.
boolean
Show all components, ignoring project framework. Short form: -a.

Examples

List all components for your framework:
Output:
Search for specific components:
Shows only components matching “fade”. Show all components regardless of framework:
Filter by specific framework:

helios add

Add a component to your project.

Usage

Arguments

string
required
Name of the component to install.

Options

boolean
Skip automatic dependency installation.

Examples

Add a component:
Output:
Add without installing dependencies:
This copies component files but skips npm install.

What happens when you add a component?

  1. Validation - Checks if component exists in registry
  2. Framework check - Verifies compatibility with your project
  3. File copying - Downloads and copies component files to your project
  4. Dependency installation - Installs required npm packages
  5. Config update - Adds component to helios.config.json

helios list

List components installed in your project.

Usage

Examples

Output:
If no components are installed:

helios update

Update an installed component to the latest version.

Usage

Arguments

string
required
Name of the component to update.

Options

boolean
Skip confirmation prompt. Short form: -y.
boolean
Skip automatic dependency installation.

Examples

Update a component:
Output:
Update without confirmation:

Warning

Updating overwrites local changes to the component. Use helios diff first to review changes.

helios remove

Remove a component from your project.

Usage

Arguments

string
required
Name of the component to remove.

Options

boolean
Skip confirmation prompt. Short form: -y.
boolean
Remove from config but keep files on disk.

Examples

Remove a component:
Output:
Remove from config only:
This removes the component from helios.config.json but leaves files untouched. Remove without confirmation:

helios diff

Compare your local component files with the registry version.

Usage

Arguments

string
required
Name of the component to compare.

Examples

Check for differences:
If there are no changes:
If there are changes:

Use cases

Before updating:
After customization:

Component workflow

Adding and using a component

Then use in your composition:

Keeping components up to date

Managing customized components

If you’ve customized a component:

Component ownership

Helios follows the Shadcn model:
  • Components are copied into your project (not installed as npm packages)
  • You own the code and can modify it freely
  • Updates are opt-in - you control when to pull registry changes
  • No lock-in - components are just source files in your repo

Registry configuration

Customize the component registry in helios.config.json:
Components are installed to the directory specified in directories.components.

See also