After researching UI component libraries, PrimeVue is the top choice for our UI development needs.
The following are my findings.

• themes: pass through
  • pass-through functionality ensures a smooth and customizable theming experience
• API: props, events, etc, easily customisable
  • ease of customization
• Styles: PrimeVue offers two modes, styled or unstyled components
• TreeShaking: Treeshaking
  • optimizes the bundle size by excluding unnecessary components
• bundle: PrimeVue is very light and fast
• Docs: easy to follow.

Library Stats:

• PrimeVue:

  • Updated: 10 days ago
  • Created: 6 years ago

• Vuetify:

  • Updated: 9 days ago
  • Created: 8 years ago

• NuxtUI:

  • Updated: 1 day ago
  • Created: 2 years ago

UI Component Libraries Comparison:

• PrimeVue vs. Vuetify:
  • PrimeVue focuses on Vue.js; Vuetify is a comprehensive framework for Vue.js, React, and Angular.
  • PrimeVue offers dedicated Vue.js components.

Feature Set:

• Both provide a range of UI components.
• PrimeVue:
  • 80+ UI Components
  • Styled or Unstyled
  • mobile support
  • Typescript support
  • Treeshaking support
• Vuetify:
  • responsive grids
  • built-in icons
  • powerful CLI
  • Treeshaking
  • SASS variables
  • Layouts
  • Global configuration

Styling and Theming:

• PrimeVue uses CSS variables for customization.
• Vuetify has a built-in theming system.

Size and Performance:

• PrimeVue is lightweight with excellent performance, using a 'tree-shaking' approach.
• Vuetify has a larger footprint but includes optimization features like lazy-loading.

Community and Support:

• Both have active communities, good documentation, tutorials, and support channels.
• PrimeVue has a smaller community, while Vuetify, being more established, has a larger community and extensive documentation.

I had consider NuxtUI but looking at the following cons against the above pros of PrimeVue I decided against NuxtUI.
NuxtUI

Cons:

• NuxtUI:
  • Locked into Nuxt framework.
  • Considered young.
  • Built with Headless UI and Tailwind CSS.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: The following managers configured in enabledManagers are not supported: "pnpm"

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Invalid schedule: Failed to parse "every 1 hour after 00:00 and before 23:59 every day"

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update all non-major dependencies (@unocss/reset, @vitest/coverage-v8, husky, pnpm, sass, sass-loader, typescript, vitest, vue, vue-router)
• chore(deps): update nuxt (@nuxt/eslint, @nuxt/image, @nuxt/test-utils, @nuxtjs/device, nuxt)
• chore(deps): update dependency eslint to v9.11.1
• chore(deps): update dependency @nuxtjs/sitemap to v6
• chore(deps): update dependency happy-dom to v15
• chore(deps): update dependency nuxt-gtag to v3
• chore(deps): lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

test