iconLibrary in components.json not reflected in generated components

[hetari]

I initialized a project using a custom icon library:

bunx --bun shadcn-vue@latest init --icon-library hugeicons

The generated components.json correctly includes:

{
  "iconLibrary": "hugeicons"
}

Then I added all components:

bunx --bun shadcn-vue@latest add --all

After generation, I inspected the codebase:

$ grep -r --include="*.vue" "from \"lucide-vue-next\"" .
# shows a lot of components
$ grep -r --include="*.vue" "from \"@hugeicons/vue\"" .
# show nothing

Result:

• No components import from @hugeicons/vue
• Many components import from lucide-vue-next

Example:

import { ChevronDown } from "lucide-vue-next"

Observation

There is a mismatch between components.json configuration and the generated component code.

Clarification needed

• Is iconLibrary expected to affect all generated components?
• Is support partial or limited to specific templates?
• Or is this configuration not yet enforced during generation?

[MILLERMARRU]

iconLibrary support is real but not universal across every generated component yet, which is why you're seeing the split. Newer registry components (the ones under the reka/ui base) render their internal icons through an IconPlaceholder helper that maps to a different icon per library, for example DropdownMenuSubTrigger's chevron resolves to ChevronRightIcon for lucide, IconChevronRight for tabler, ArrowRight01Icon for hugeicons, and so on depending on your configured iconLibrary. Components built on that pattern do respect the setting correctly.

The ones still importing directly from lucide-vue-next haven't been migrated to IconPlaceholder yet, they're hardcoded to lucide regardless of what components.json says. That's almost certainly what you're running into with --add --all, a mix of migrated and not-yet-migrated components in the same batch.

One more thing worth checking on your setup specifically: the current lucide package for shadcn-vue is @lucide/vue, not lucide-vue-next (that's the older/renamed package). If your generated components are pulling from lucide-vue-next specifically, it's worth confirming which registry/version your CLI resolved against, since that's a signal you may be getting components from an older snapshot of the registry rather than the current dev one.

Practical path for now: for any component that shows up hardcoded to lucide-vue-next after --add --all, treat the icon import as something you own post-generation (which is the whole shadcn model) and swap it manually for your chosen library's equivalent icon. Re-running add for a specific component name after the maintainers migrate it to IconPlaceholder should pick up the fix automatically once that lands.