Hi @wary hearth. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#`#components` conflict when auto-importing components from an external package
wind acornBOT
I'm sorry, but the knowledge sources do not contain explicit information about resolving conflicts when an external package uses the #components import mapping, which then clashes with Nuxt's own #components alias during auto-imports via a module.
The documentation does explain how to use addComponent to auto-import components from npm packages and how Nuxt's #components alias works for direct imports and auto-imports, but it does not address alias conflicts with external packages or provide a built-in way to namespace or remap the #components alias for dependencies. The only workaround mentioned in the sources is to change the import mapping in the external package, which you already noted works, but you are seeking a solution that does not require modifying the package itself.
If you need further assistance, you may want to open an issue on the Nuxt GitHub repository or discuss with the Nuxt community for potential workarounds or upcoming features that could address this scenario.
References:
- Direct Imports and #components alias
- addComponent usage for npm packages
- Auto-imported components and configuration