perf!(nuxt3): disable global components by default

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#12903

❓ 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 like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This change defaults to only using the loader to register components, rather than generating async chunks for every possible component. (This makes a huge difference with component libraries, as we don't need to compile all of their components, just the ones needed.)

This also adds a top-level components.global option to set the default value for component dirs which haven't set the global value.

👉 Migration

If you were relying on global registration of your components - for example, because you wanted to use a dynamically computed component name (e.g. <component :is="'icon-' + myIcon" />) then you can re-enable the previous behaviour by setting components.global:

  import { defineNuxtConfig } from 'nuxt3'
  
  export default defineNuxtConfig({
    components: {
+     global: true,
+     dirs: ['~/components']
    },
  })

📝 Checklist

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

[netlify]

✔️ Deploy Preview for nuxt3-docs canceled.

🔨 Explore the source changes: 1ad8616

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/620eec579dc30400087cbd6e