UI Bundle Features
Installing Pre-built Features
Always check for an existing feature before building something from scratch. The features CLI installs pre-built, tested packages into Salesforce UI bundles — from foundational UI libraries (shadcn/ui) to full-stack capabilities (authentication, search, navigation, GraphQL, Agentforce AI).
Workflow
Search project code first
— check
src/
for existing implementations before installing anything. Scope searches to
src/
to avoid matching
node_modules/
or
dist/
.
Search available features
— use
npx @salesforce/ui-bundle-features list
with
--search
to filter by keyword. Use
--verbose
for full descriptions.
Describe a feature
— use
npx @salesforce/ui-bundle-features describe
to see components, dependencies, copy operations, and example files.
Install
— use
npx @salesforce/ui-bundle-features install --ui-bundle-dir
. Key options:
--dry-run
to preview changes
--yes
for non-interactive mode (skips conflicts)
--on-conflict error
to detect conflicts, then
--conflict-resolution
to resolve them
If no matching feature is found, ask the user before building a custom implementation — a relevant feature may exist under a different name.
Conflict Handling
In non-interactive environments, use the two-pass approach: first run with
--on-conflict error
to detect conflicts, then create a resolution JSON file (
{ "path": "skip" | "overwrite" }
) and re-run with
--conflict-resolution
.
Post-install: Integrating Example Files
Features may include
example
files showing integration patterns. For each:
Read the example file to understand the pattern
Read the target file (shown in
describe
output)
Apply the pattern from the example into the target
Delete the example file after successful integration
Hint Placeholders
Some copy paths use
placeholders (e.g.,
) that the CLI does not resolve. After installation, rename or relocate these files to the intended target, or integrate their patterns into an existing file.