Type alias vs inline types in Typescript - When to Use Which

The Big Idea

What if you could fix a type mistake once and watch it update everywhere automatically?

The Scenario

Imagine you are writing a program where you need to describe the shape of many objects, like user profiles or product details, by writing the same type structure over and over again directly inside your code.

The Problem

Writing the same type details repeatedly makes your code long, hard to read, and easy to make mistakes. If you want to change the structure later, you have to find and update every place manually, which is slow and error-prone.

The Solution

Using a type alias lets you give a name to a type structure once, then reuse that name everywhere. This keeps your code clean, easy to read, and simple to update in one place.

Before vs After

✗ Before

function greet(user: {name: string; age: number}) { console.log(user.name); }
function showAge(user: {name: string; age: number}) { console.log(user.age); }

✓ After

type User = {name: string; age: number};
function greet(user: User) { console.log(user.name); }
function showAge(user: User) { console.log(user.age); }

What It Enables

It enables writing clearer, shorter, and more maintainable code by reusing type definitions easily.

Real Life Example

When building a website with many forms collecting user info, using type aliases for user data helps keep all form validations consistent and easy to update.

Key Takeaways

Writing inline types repeatedly makes code long and error-prone.

Type aliases let you name and reuse types for cleaner code.

Changing a type alias updates all uses instantly, saving time.