feat(nuxt)!: only scan top level composables/ and support glob

[antfu]

🔗 Linked issue

unjs/unimport#86 (comment)

Unimport upgraded from 0.4.x to 0.6.x in #6032

❓ 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

This PR changes auto-imports' behavior to exclude nested folders from auto-imports.

To get auto imports for nested modules, you can re-export them from composables/index.ts (see alternative below)

// composables/index.tsexport{usebar}from'./utils/bar.ts'

👉 Migration

⚠️ Breaking change: composables/*/index.ts is no longer being scanned and you need to reexport. In order to preserve previous behavior, please configure autoImports.dirs:

exportdefaultdefineConfig({// ...autoImports: {dirs: ['composables',// top-level modules'composables/*/index.{ts,js,mjs,mts}'// one level directories's index.js,//'composables/**', // Scan all nested directories]}})

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit	c49fcd8
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62d95c915021970009c0b934
😎 Deploy Preview	https://deploy-preview-6025--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[danielroe]

Looks good to me.

[pi0]

Seems a good defaults change to simplify scanning with top level only. Can you please:

• Update PR description for breaking change and migration guide (to link from release notes)
• Split the nested composables example from simple one to the end of docs page
• Suggest composables/index.ts for reexports
• Swap two options for nested to prefer top-level file over configuration

[danielroe]

Updated migration guide whilst @pi0 was reviewing. One thought: we should also update logic for other scanned directories, likely in same PR to reduce breaking change.

[pi0]

surely we need to make scanned directories to a closer behavior. But let's keep changes splitted. @danielroe What other dirs are you thinking?

[danielroe]

Plugins currently have this /index behaviour. Middleware and layouts are also scanned at a single level with no way to configure it. (Which might be okay, but see also #5842.)

[pi0]

Strict behavior of middleware/layouts makes sense. We can add option later without breaking changes. (breaking) Change for plugins makes sense with same next release 👍🏼

[pi0]

PR description: I would suggest to add top level index.ts reexport (convention over configuration) as recommended migration path.

[antfu]

Migration guide updated. Let me know if you have any other suggestion, or update it directly :)

[pi0]

(upgraded mistakenly merged via previous #6032 PR). Latest edge release contains the changes via merge commit of this.