Default type imported with `import type` from not-found module not flagged when used as a value about typescript HOT 3 OPEN

Works well for me. I think your issue is caused by @ts-expect-error? I would suggest using bug workbench instead of playground since the former one could handle import/export between multiple files.

https://www.typescriptlang.org/dev/bug-workbench/?#code/PTAEAEDMEsBsFMB2BDAtvAXKVB7AJgHQAuAzgFBECeADvKACqgC8oiArqgEbwBOA3GXgAPajh5FQeeJGRtYE+gOGjxoAN6gqtBqGQlQAVVABfAWRAQYCFOizJq1YuWioVErXUaQeOVKABEBMC4eP4CAMY4iCTuzAxmLm7qmjR0Rsag3r6gAORBITkRUTGgbHEGAkA

from typescript.

think your issue is caused by @ts-expect-error?

It is not - the comment specifically only applies to the import source - hence the weird placement.
Also note in your bug workbench the placement of the error - it is on the const t = T;, not on the import declaration.

Also TIL about the bug workbench. I hadn't seen that before.

It looks like this specifically occurs then if the imported module does not exist.

from typescript.

It looks like this specifically occurs then if the imported module does not exist.

Does that matter, then? To be clear it's still a bug since you shouldn't be able to use type imports in value positions, but in practice you already get an error on the import, and I don't think people are generally going to be @ts-ignoreing module resolution errors.

from typescript.