fix: prefer disabling imports with imports.autoImport

[wattanx]

🔗 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

The #imports alias is set inside the import module.
So even if imports: false, I think you need to run import module.

In Nuxt 3, I believe the import module is executed even with autoImport: false.
https://github.com/nuxt/nuxt/blob/master/packages/nuxt/src/core/nuxt.ts#L406-L412

(I am wondering if I should be able to set it with the imports.autoImport option like in Nuxt 3.)

📝 Checklist

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

[danielroe]

I think we should probably still respect imports: false but warn when this is enabled, and suggest instead that they set imports.autoImports: false.

[wattanx]

@danielroe
Thanks for the review!
I agree with your opinion!
I added a warning in the following commit.
1dfe562