Nuxt · Imports
NUXT0019Nested composables are not auto-imported by default
Flags nested autoimport assumption in Nuxt composables code before it leaks into runtime behavior.
vite-doctor/nuxtimportswarnSuggestion
Why it happens
Auto-imports are global within a project. Explicit names and imports prevent local code from shadowing framework composables.
Fix
Remove nested autoimport assumption, or move it to the Nuxt runtime/API that owns that behavior.
Example
Export nested composables explicitly
Before
// app/composables/nested/useThing.ts
export function useThing() {
return useState('thing')
}
After
// app/composables/useThing.ts
export { useThing } from './nested/useThing'
Verify the fix
Run only this rule after editing so the report stays focused on the diagnostic you are closing:
pnpm nuxt doctor --rules nuxt/composables/no-nested-autoimport-assumption