fix(nuxt): handle schema types for relative module paths

[danielroe]

🔗 Linked issue

❓ 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

In the case where a module is specified with a relative path, it is not properly typed in schema.d.ts. For example:

exportdefaultdefineNuxtConfig({modules: ['../src/module'],})

results in the following type:

declare module '@nuxt/schema'{interfaceNuxtConfig{["metaKey"]?: typeofimport("../src/module").defaultextendsNuxtModule<infer O> ? Partial<O> : Record<string,any>}}

But this relative import path either needs to be absolute or resolved relative to the generated schema.d.ts.

📝 Checklist

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

[codesandbox]

Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	afa2e34
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/633834149688400010d033cd

[atinux]

LGTM

[pi0]

Have you tested if it also works with extends layers that have different relative root?

[danielroe]

Could you explain more? If an extends layer adds a module with a relative path I suspect it wouldn't work at all, quite apart from this PR.