fix(nuxt): exclude plugin declaration from non-existent files

[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR fixes an issue where non-existent (i.e. virtual) plugins would cause type inference for plugin injections to fail.

📝 Checklist

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

[IlyaSemenov]

I was wondering if this could be somehow backported to 3.4.x with some kind of user-land code? Type inference breaks in <3.5.1 due to InjectionType<typeof import("../components.plugin").default> which is fixed here.

[IlyaSemenov]

OK, it was actually simple:

// Fix useNuxtApp() return type missing data injected by plugins.
//
// The problem was fixed in Nuxt 3.5.1, please remove after upgrading.
// See https://github.com/nuxt/nuxt/pull/20974#issuecomment-1592724945

import { addTemplate, defineNuxtModule } from '@nuxt/kit'

export default defineNuxtModule({
  setup(_option, nuxt) {
    addTemplate({
      getContents: () =>
        'declare const _default: any; export default _default;',
      filename: 'components.plugin.d.ts',
      dst: nuxt.options.buildDir + '/components.plugin.d.ts',
      write: true,
    })
  },
})