Skip to content

Conversation

@calmyournerves
Copy link
Contributor

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

After updating to @nuxt/ui 3.3.0 we got a Failed to resolve component: UBadge error for the Tabs component (Badge support was added to Tabs in #4553. We're using a custom prefix for the components. This PR explicitly imports UBadge to fix this.

@calmyournerves calmyournerves changed the title fix: Explicitly import UBadge to make Tabs component work with custom prefix fix(Tabs): Explicitly import UBadge to make Tabs component work with custom prefix Jul 25, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Jul 25, 2025

npm i https://pkg.pr.new/@nuxt/ui@4594

commit: 70573fd

@benjamincanac benjamincanac changed the title fix(Tabs): Explicitly import UBadge to make Tabs component work with custom prefix fix(Tabs): add missing Badge import Jul 27, 2025
@benjamincanac benjamincanac merged commit fbec29c into nuxt:v3 Jul 27, 2025
6 checks passed
@benjamincanac
Copy link
Member

Thanks 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v3 #1289

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants