Introduction to Type Aliases
Understand Introduction to Type Aliases
A type alias gives a reusable name to any TypeScript type, including primitives, unions, tuples, and object shapes.
What you will learn: the purpose of introduction to type aliases, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.
What you’ll learn
- Explain how introduction to type aliases works and where its type rules apply.
- Predict the exact output of the introduction to type aliases example.
- Diagnose a common issue: Do not attempt new Product(): a type alias is not a class or value at runtime.
Build the mental model
Type aliases are erased from JavaScript and are not runtime constructors or validators. They help keep contracts consistent without duplicating long inline annotations. A type alias name does not create nominal identity in TypeScript’s structural type system.
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.
See the relationship
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.
Run the complete TypeScript example
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
type ProductId = string;
type Product = { id: ProductId; price: number };
const product: Product = { id: "P-12", price: 199 };
console.log(`${product.id}: ₹${product.price}`);Verified output
P-12: ₹199Run 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.
Trace every important step
ProductId names the string type and Product names an object shape. The runtime product is a normal object with id P-12 and price 199.
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.
Avoid these common mistakes
Do not attempt new Product(): a type alias is not a class or value at runtime. Type aliases are not a substitute for validating API responses.
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.
Practice and experiment
Create a Currency type alias for "INR" | "USD" and use it in a Price object type.
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.
Check your understanding
Review the key idea
Introduction to Type Aliases: A type alias gives a reusable name to any TypeScript type, including primitives, unions, tuples, and object shapes.
ProductId names the string type and Product names an object shape. The runtime product is a normal object with id P-12 and price 199.
Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.
Reaching the recap and completing the quizzes are separate milestones.