feat(kit): provide type support for module options in installModule

[ineshbose]

🔗 Linked issue

📚 Description

These changes relies and builds on top of #18416 (my first PR on Nuxt 😄); it extracts the options from there after module authors run prepare.

Try this in the repo playground:

import { installModule } from "@nuxt/kit";

installModule('@nuxt/devtools', { customTabs: [] })

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[ineshbose]

this doesn't seem to be picking up because .nuxt/types/schema.d.ts now seems to be using resolved paths, i.e.

declare module 'nuxt/schema' {
  interface NuxtConfig {
    modules?: (["/home/nuxt/nuxt/test/fixtures/basic-types/modules/example", Exclude<NuxtConfig["sampleModule"], boolean>] | ["@nuxt/devtools", Exclude<NuxtConfig["devtools"], boolean>])[],
  }
}

so where T = '~/modules/example', it is not equal to /home/nuxt/nuxt/test/fixtures/basic-types/modules/example; so this will work for package names more than local modules, sure, but I'm not sure how the usage ahead of ['~/modules/example, { typeTest: () {} }] worked even when the path isn't same 🤔

[ineshbose]

but I'm not sure how the usage ahead of ['~/modules/example, { typeTest: () {} }] worked even when the path isn't same

it's likely that its just the TypeScript is quite relaxed with all the union options.

[ineshbose]

it should work now; also note that (as I had thought), we're doing a dynamic import of NuxtConfig within types (edit: CI still failing... hmm)