[no-extraneous-dependencies] improve validation of "import type"

at the moment if I do this rule is not checking dependency: import type {TypeA} from 'ModuleA'

would be nice if such import would be checked against combination of dev and prod dependencies.

[ilyub]

+1 for an option “alsoCheckTypeDependencies” or additional rule “noExtraneousTypeImports” with same options as “noExtraneousImports”.

Typescript libraries are usually distributed as .js + .d.ts.

If your .ts file imports types from package A and consuming project does not have package A, it will fail to understand types defined in .d.ts.

So, even if you only import types from package A you may need to add it to dependencies or peer dependencies.

Sonarqube does not ignore type import by the way.

[ljharb]

While I think that’s the common case, we couldn’t just impose that on everyone - you’d need to be able to opt in to it somehow.