Components Discovery

[pi0]

• Initial working version from @nuxt/components
• .dts generation
• Decide about prefix
• Implement loader strategy (vite and webpack5)
• Integrate with devtools

Discussion: Should we even have it with nuxt3?

Related tweet (https://twitter.com/youyuxi/status/1404795327144763398). I think that makes sense in many ways that auto-import is not that needed with new <script setup> syntax and better VSCode integrations. But there are still some cases most notable, CMS/Content integrations that implicitly need global components. And also this gives possibility with nuxt devtools component playground

Discussion: Where to implement?

In framework/packages/components as a fork of nuxt/components and add by default in nuxt3

Discussion: Prefixing

Should we use (by default) one level prefix components/utils/bar/baz => BarBaz or full prefix => UtilsBarBaz or not at all (Baz) by default (suggested by @Atinux). Second is much more future proof but less convenient for structuring components dir based on purpose (and atomic designs)

[antfu]

For some related info:

• https://twitter.com/patak_js/status/1405565173084168197
• https://twitter.com/antfu7/status/1403281833555488769
• types(defineComponent): Support for GlobalComponents, typed Directives and respect expose on defineComponent vuejs/core#3399

[Atinux]

What is the state of this issue regarding the loaders @antfu ?

[antfu]

Do you mean the resolvers? Will work on Nuxt 2 @nuxt/components first (this week) and port to Nuxt 3 later

[pi0]

Resolver support: nuxt/components#231 / Loader is already implemented

[pi0]

Leaving devtools integration to the future.