refactor(nuxt)!: rename autoImports to imports

[antfu]

🔗 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

As this feature now goes beyond just auto-imports, the naming autoImports becomes a bit confusing and ambiguous. See #6768 for more.

This PR renames Nuxt option autoImports to imports and hooks autoImports:* to imports:*. This also aligns with components option.

👉 Migration

⚠️ Breaking change: Nuxt option autoImports named to imports. Hooks autoImports:* renamed to imports:*.

for nuxt.config.ts:

export default defineConfig({
  // ...
- autoImports: {
+ imports: {
    // ...
  }
})

for module authors:

-nuxt.hook('autoImports:extend', () => { })
+nuxt.hook('imports:extend', () => { })

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	717541c
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6304e1d69f6c000009f9e3a8

[pi0]

I really love renaming of this PR and I think it worth it doing for both nuxt and nitro ( @antfu do you mind to open a PR for it)

Only issue is with deprecation of hooks it doesn't works because we set deprecated hooks in auto imports module and it happens after other modules and hooks by user config are registered. It could be a big breaking change I like to avoid.

[antfu]

Nitro PR: unjs/nitro#433

Hook timing: Is 9c5b034 a good solution?

[pi0]

Thanks for both. Hookable issue is solved via unjs/hookable@23d9ff4 btw we can revert it back and try :)