Consider enabling @typescript-eslint/no-import-type-side-effects

[spence-s]

Currently @typescript-eslint/consistent-type-imports auto fixes all type imports to be inline.

If an import only includes type imports this will result in an empty module import.

https://typescript-eslint.io/rules/no-import-type-side-effects

This rule seems to be complimentary to consistent-type-imports and doesn't conflict but adds extra safety when the verbatimModuleSyntax ts config flag is turned on.

[sindresorhus]

I kinda prefer the consistency of always using inline type.

[spence-s]

That's fair, its simple enough to add this rule for myself, and since you don't have verbatimModuleSyntax turned on in your tsconfig, I believe TS will strip the entire import away even with only an inline type.

For me, the need to turn this rule on comes from switching to use Node.Js native type stripping where I can (when it makes sense), and Node will leave the "dangling import" and only strip the inline type, which sometimes leads to unexpected imports and errors.

see: https://nodejs.org/api/typescript.html#type-stripping

Feel free to close this if you're still not convinced :)

[EdJoPaTo]

Since the behaviour of Node.js when using TypeScript files directly is just type stripping is using verbatimModuleSyntax (see https://nodejs.org/api/typescript.html#type-stripping) it's likely a good idea to follow the behaviour of Node.js.

Maybe it's consistent when always using inline type but having the side effect behaviour might be confusing and import type is the explicit version of preventing that. And personally prefer something that prevents confusing behaviour.