Type Compatibility and Type System Limitations

TypeScript primarily uses structural compatibility: a value is assignable when it has the required shape. Additional fields can be present, and types are erased at runtime. Some compromises preserve JavaScript interoperability rather than guaranteeing soundness for all patterns.

Reading the code: person has at least the name property required by Named, so the assignment is valid. Although the variable is typed Named, its runtime object still contains role. The in check finds it.

Keep the boundary clear: An assignment to a narrower static type does not strip extra runtime fields. Excess-property checks also differ for fresh object literals versus existing variables.

Save the code as type-compatibility-type-system-limitations.ts. The result below was captured after compiling this exact example with strict TypeScript checking and executing the emitted JavaScript in Node.js.

TypeScript code

type Named = { name: string };
const person = { name: "Ava", role: "editor" };
const named: Named = person;
console.log(named.name);
console.log("role" in named);

Verified output

Ava
true

Build: npx tsc --strict --target es2022 --module commonjs --lib es2022,dom,esnext.disposable type-compatibility-type-system-limitations.ts; run: node type-compatibility-type-system-limitations.js. The exact filename may be changed freely. When a multi-file project exists, prefer its tsconfig.json and build scripts.

person has at least the name property required by Named, so the assignment is valid. Although the variable is typed Named, its runtime object still contains role. The in check finds it.

The output shown above comes from the initialized values in this program. Replacing a type annotation alone does not transform a JavaScript value.

An assignment to a narrower static type does not strip extra runtime fields. Excess-property checks also differ for fresh object literals versus existing variables.

Check both the TypeScript diagnostic and the emitted JavaScript behavior. A program can compile correctly and still need runtime validation or error handling.

Try assigning {name:"Ava",role:"editor"} directly to a Named variable and explain the fresh-literal diagnostic.

Before running your change, write down the type you expect TypeScript to infer and the output you expect JavaScript to print. Then check both predictions.

TypeScript primarily uses structural compatibility: a value is assignable when it has the required shape.

Try the practice change and re-run the exact program to test your understanding.