refactor: refactor import { type foo } to import type { foo }

[shinGangan]

🔗 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)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

import type { foo } and import { type foo } were mixed, so I refactored it to import type { foo }.

• related: https://nuxt.com/blog/v3-8#type-import-changes

Note

Refactoring after the official release is hard, so I fixed it first.

[vercel]

@shinGangan is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

[harlan-zw]

Thanks! Ideally, the nuxt eslint rules would cover this.

[shinGangan]

Thanks! Ideally, the nuxt eslint rules would cover this.

@harlan-zw , I feel the same way.
Nuxt ESLint has rules set, so the problem may be with the typescript-eslint rules themselves.
(Can it not be detected in a case like this?🤔)

• Nuxt ESLint: rules
• setting rules: https://typescript-eslint.io/rules/consistent-type-imports/

I'll also look into the rules of typescript-eslint when I have time.