Object Type Annotations

An object type annotation lists the properties and their expected types. It provides a contract for the object shape.

What you will learn: the purpose of object type annotations, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.

Structural typing checks the properties rather than requiring a named class instance. Inline annotations are fine for small one-off values; reuse interfaces or type aliases for larger contracts shared across functions.

Key distinction: TypeScript checks the declared types during development; emitted JavaScript carries out the value-level operation at runtime. A type declaration alone never validates untrusted runtime input.

Read this illustration from the first labeled part to the last. Compare it with the example and identify which parts are type checks and which parts run in JavaScript.

This self-contained example uses fixed values, so it runs without reading input or depending on an external service. Paste it into the TypeScript Playground or save it as main.ts.

TypeScript program

const ticket: { id: number; status: string } = {
  id: 101,
  status: "open"
};
console.log(`${ticket.id}: ${ticket.status}`);

Verified output

101: open

Run locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. For projects with a tsconfig.json, build using that configuration instead.

TypeScript checks that id is a number and status is a string. The JavaScript object contains ordinary id and status fields and prints 101: open.

Check each step: identify the input values, follow the JavaScript operation in execution order, and match the final expression with the exact output shown. An annotation can reject invalid source before execution, but does not change the value printed.

Adding id: "101" is a type error; it does not automatically parse a numeric identifier. Do not assume type annotation syntax performs input validation.

How to debug: reproduce the issue in a minimal example. For compiler errors, inspect the inferred and declared types; for a runtime surprise, log the actual values and follow their references or branches.

Annotate an object with name: string, price: number, and available: boolean. Try omitting each required property.

Practice routine: predict the result on paper, edit one part of the code, compile under --strict, run the JavaScript, and explain whether TypeScript caught an error or JavaScript simply behaved differently.

Object Type Annotations: An object type annotation lists the properties and their expected types.

TypeScript checks that id is a number and status is a string. The JavaScript object contains ordinary id and status fields and prints 101: open.

Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.