it looks like it can be replaced with just import type {} syntax instead?

This is what I was afraid of. this will produce wrong output in the following case (or similar, I didn't check exactly this code but it should give you the idea):

// index.ts
import { MyClass } from 'some-lib';
import { ParentType } from './other';

export class Foo extends MyClass {
    field: ParentType;
}

// other.ts
import { type MyClass } from 'some-lib';

export type ParentType = MyClass;

Technically if a type was used as a "value", then it should be imported as a "value" even if there are imports of as a "type". But on the other side, there are cases where you might have mixed imports and mixed usage, and then re-export of "type" import but if we import it as "value" then it might be re-exported with a wrong meaning:

// index.ts
import type { MyClass } from 'some-lib';
import { FooBar } from './other';

export type MyClassType = MyClass;

// other.ts
import { MyClass } from 'some-lib';

export class FooBar extends MyClass {}

In this case the output might be the following:

import { MyClass } from 'some-lib';

export type MyClassType = MyClass;
export class FooBar extends MyClass {}

which looks correct, but it might have implications in other places (I need to play with this more to give you an example if there is one). Or it could be

import type { MyClass } from 'some-lib';

export type MyClassType = MyClass;
export class FooBar extends MyClass {}

Which is broken because 'FooBar' cannot be used as a value because it was imported using 'import type'.

That's why #290 exists and why initially I thought that #320 is a duplicate and then re-opened, but it seems I'm leaning to think about it as about a duplicate aging based on said above...

The issue is that compiler doesn't tell you whether a symbol/node was originally value but was used a type or anything like that (see microsoft/TypeScript#57032 for more context).

Great reply! Haven't had time to digest but can hopefully sit down and think about this and push something. Appreciated!

It does look like we kinda need what's noted in the TypeScript issue. Will dig around and see what we can use otherwise.

oh please try to avoid using types from any of dependencies - they tend to change between releases and it will cause tests to fail without changing (almost) anything. If you need some specific pattern of a package, you can add it here https://github.com/timocov/dts-bundle-generator/tree/master/tests/e2e/test-cases/node_modules or use any existing one there