Skip to content

Conversation

@ISOR3X
Copy link

@ISOR3X ISOR3X commented Nov 22, 2025

πŸ”— Linked issue

Resolves #4892

❓ 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

Allows adding external packages to be scanned for Nuxt UI components through the new allowedPackages option. This allows using Nuxt UI as a dependency for other projects.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@github-actions github-actions bot added the v4 #4488 label Nov 22, 2025
@ISOR3X
Copy link
Author

ISOR3X commented Nov 22, 2025

I wasn't sure about the name or location for the option. Besides the current option, I also considered extending ComponentsOptions since feature mostly relates to unplugin-vue-components. In the end I decided against it to keep that key purely for the options from that package.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 22, 2025

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

commit: fc02356

@benjamincanac
Copy link
Member

I'm wondering if it wouldn't be easier to just remove this exclude, do you have a reproduction to try if it doesn't decrease performances?

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

Labels

v4 #4488

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using Nuxt UI in components from a npm package, in Vue

2 participants