Imported type incorrectly allowed to be used as a value when object shorthand is used

[samouri]

Bug Report

Normally, TS will figure out if an imported type is incorrectly being used as a value.
When shorthand object creation is used, TS will miss the error.

⏯ Playground Link

I couldn't figure out how to use the playground since it depends on using multiple files (import/export).
I've created a minimal repro in this repo samouri/typescript-type-import-bug-repro, it is only ~10 LOC.

💻 Code

import type { A } from './a';

// This correctly throws
const object1 = {A: A}

// This should throw the error: "'A' cannot be used as a value because it was imported using 'import type'"
const object2 = { A };

🙁 Actual behavior

No error is thrown

🙂 Expected behavior

An error should be thrown. Types should not be used where values are expected.

[orta]

Strange, this seems to raise 2693 correctly in the TS bug workbench

// @errors: 2693
// @filename: other.ts
export type A = {
    thing: string
}
// @filename: index.ts
import type { A } from './other';

// This should throw the error: "'A' cannot be used as a value because it was imported using 'import type'"
const object = { A }; 

Workbench Repro

[samouri]

If you change the type to a class then it will reproduce.

// @filename: other.ts
export class A {}

// @filename: index.ts
import type { A } from './other';

// This should throw the error: "'A' cannot be used as a value because it was imported using 'import type'"
const object = { A }; 

Workbench Repro

[samouri]

Thank you for fixing this so quickly!
Is there any way for me to track which release this makes it into?

[RyanCavanaugh]

@samouri this will be in TypeScript 4.4 (the RC and final, but not the beta which has already passed).