[Question | Feature request] Disable Auto-import components feature ( Fully tree shakable ? )

As the title suggests, I'm facing an issue where I have a separate repository for common components, which I build using Vite and link to the package.json in the main project that runs Nuxt.

When I run the Nuxt project in development mode, everything works fine. However, when building for production, I need to follow these steps:

1. Build the common components repository.
2. Build the main project, which uses the built files from the common repository.

The problem arises after the first step. Since the common components repository doesn't use Nuxt, the build output doesn't include the necessary Vuetify components.

I know I can manually add an import line inside the common components to import the required Vuetify components. However, during development, this can be confusing for other team members (who have limited knowledge of Nuxt and auto-import functionality), as TypeScript and Nuxt recognize the Vuetify components without explicit imports and show no errors. But after building, it just doesn’t work.

TL;DR: Is there a way to disable the auto-import components feature?

What I tried:

nuxt.config.ts

  vuetify: {
    moduleOptions: {
    },

    vuetifyOptions: {
      components: false,
    },
  },

Start with nuxt.config.ts and the moduleOptions/vuetifyOptions.components setting shown in the issue. Reproduce the two-step Vite and Nuxt production build using the linked common-components repository, then determine the supported configuration for disabling component auto-import. Done means the common components build includes the required Vuetify components without relying on Nuxt auto-imports.