Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Link to the rule's documentation

https://typescript-eslint.io/rules/consistent-type-imports/

Description

TypeScript 5.0 is introducing a new --verbatimModuleSyntax flag/option, that enforces type imports to output exactly as they are written, rather than letting the compiler decide. One of the noted output conditions of this is that import { type xyz } from "xyz"; will be rewritten to import "xyz";. This means inline type imports can and will still result in the file ending up imported. While this will always happen with this option enabled, it's also possible for it to happen currently if TypeScript decides to import it.

As this introduces potential unwanted imports, I propose a new option to disallow imports that purely contain inline type imports. The option could then add an auto-fixer to move the type import to the base of the import rather than inline. Eg, from import { type a } from './xyz'; -> import type { a } from './xyz';

Fail

import { type a, type x } from './xyz';

Pass

import { a, type b } from './xyz';

import type { b } from './xyz';

Additional Info

No response