Rule Suggestion: require-import-type-modifiers

[Nokel81]

With the release of typescript 4.5, it is possible to have type Modifiers on Import Names.

It would be great if there was a (fixable) rule that could be used to require these.

I am willing to implement this.

[ljharb]

It seems better to require them be separate import type statements.

[Nokel81]

Not if there are only one or two of either kind. But that could be a different option I guess.

[ljharb]

It seems unfortunate to have a rule that is only useful for typescript, but perhaps a rule that detects your TS (or flow) version, and can be configured for an order of preferences - ie, between "types as separate import statements", "types mixed with values, but marked with a type modifier", you could prefer one over the other, and it would fall back to the next one if the preferred one wasn't supported, and if neither are supported, the rule would noop.

[yume-chan]

@typescript-eslint/consistent-type-imports can enforce type-only imports to have a type specifier.

import/consistent-type-specifier-style can choose to ban either import type or import { type }

So bad I need two rules! And the second one hasn't been released yet!