Ship internal tools in hours, not weeks. Real auth, users, jobs, audit logs, and cohesive UI included. Early access $249 $499 → [Get it now]

CoreUI PRO for Vue v5.19.0 - ChipSet, MultiSelect Enhancements & Major Improvements

CoreUI PRO for Vue v5.19.0 - ChipSet, MultiSelect Enhancements & Major Improvements

We are excited to announce the release of CoreUI PRO for Vue v5.19.0. This is a major feature release introducing the new Chip Set component, significant Multi Select enhancements, the Search Button component, Sidebar Nav tree variant, carousel touch swipe support, and many important bug fixes across PRO and core components.


Speed up your responsive apps and websites with fully-featured, ready-to-use open-source admin panel templates—free to use and built for efficiency.


How to Update

To update your project to CoreUI PRO for Vue v5.19.0, follow these steps:

  1. Open your project’s package.json.
  2. Locate the @coreui/vue-pro entry under dependencies and update the version number to 5.19.0.
  3. Find the @coreui/coreui-pro entry under dependencies and update the version number to ^5.25.1.
  4. Save your changes to the package.json file.
  5. In your project’s root directory, run the update command appropriate for your package manager:
    • For npm users, execute npm install.
    • For yarn users, execute yarn install.
    • For pnpm users, execute pnpm install.

What’s New

Features

  • CChipSet: New component for grouping chips with built-in selection coordination (single/multiple via v-model), roving focus, data-driven chips prop, v-model:chips for self-syncing removal, and v-model:selected for selection state. Supports filter chips with a leading check icon.

  • CChip - Filter Mode: Added filter prop that implies selectable and shows a check icon while selected. Disabled chips no longer render a remove button.

  • CChipInput Improvements: Now built on the shared useChipSet composable, adds selectionMode prop, always renders the hidden form input, supports initializing from slot content, and mirrors arrow-key navigation in RTL.

  • CMultiSelect Enhancements:

    • Select-all toggle with selectAllMode (all/filtered) and selectAllStyle (checkbox/text with tri-state indicator)
    • Selection limit support via selectionLimit prop
    • Selectable option groups with tri-state checkbox indicators
    • Custom dropdown header via scoped slot with state and action helpers
    • Native select overlay for browser required validation
    • Accessibility improvements: aria-live, aria-controls, search labeling, focus return
  • CSearchButton: New keyboard-shortcut-aware search trigger button displaying platform-appropriate hints (⌘K / Ctrl+K).

  • CSidebarNav - Tree Variant: Added tree variant and compact prop for hierarchical navigation structures.

  • CNavGroup - Controlled Visibility: Reworked to support controlled mode via v-model:visible, context-based accordion coordination, and auto-opening the active route.

  • CCarousel - Touch Swipe: Added touch swipe support with pointer events, RTL-aware direction mapping, and slide/slid events.

  • CDropdown, CPopover, CTooltip - popperConfig: New popperConfig prop for custom Popper.js positioning options.

Bug Fixes

  • CDropdown: Default variant corrected to 'dropdown' to match other frameworks.
  • CFormRange: Renamed steps prop to step so the interval actually applies to the range input.
  • CChip: Default selected prop to undefined to fix the controlled/uncontrolled distinction.
  • CToastClose: as prop now accepts a component, not just a string.
  • CFocusTrap: Resolves component public instance to $el so focus handling works inside <Transition>.
  • CSidebar: Removed leftover console.log in mobile watcher.

Migration Notes

This release includes a few behavioral changes:

  • CDropdown: Default variant changed from 'btn-group' to 'dropdown'. Explicitly pass variant="btn-group" if you relied on the previous default.
  • CFormRange: The steps prop has been renamed to step. Update your templates accordingly.
  • CNavGroup: Now uses provide/inject coordination instead of vnode cloning. The API is backward-compatible, but if you used internal implementation details, review the new context-based approach.

For the latest package files and update access, visit CoreUI Downloads.

Subscribe to our newsletter
Get early information about new products, product updates and blog posts.

Answers by CoreUI Core Team