Interface vs type alias decision in Typescript - Hands-On Comparison

Interface vs Type Alias Decision in TypeScript

📖 Scenario: You are building a simple contact list app. You want to store information about people including their name and phone number. You will decide whether to use an interface or a type alias to define the shape of a contact.

🎯 Goal: Learn how to create a contact data structure using both interface and type alias in TypeScript, and understand when to use each.

📋 What You'll Learn

Create an interface named ContactInterface with name and phone properties.

Create a type alias named ContactType with the same properties.

Create a variable contact1 using ContactInterface.

Create a variable contact2 using ContactType.

Print both contacts to the console.

💡 Why This Matters

🌍 Real World

Defining data shapes clearly helps avoid mistakes when building apps that handle user information.

💼 Career

Understanding when to use interfaces or type aliases is important for writing clean, maintainable TypeScript code in professional projects.

1

Create an interface for a contact

Create an interface called ContactInterface with two string properties: name and phone.

Typescript

// Your code here

Hint

An interface defines the shape of an object. Use interface ContactInterface { name: string; phone: string; }.

2

Create a type alias for a contact

Create a type alias called ContactType with two string properties: name and phone.

Typescript

interface ContactInterface {
  name: string;
  phone: string;
}
// Your code here

Hint

A type alias can also describe an object shape. Use type ContactType = { name: string; phone: string; };.

3

Create variables using interface and type alias

Create a variable contact1 of type ContactInterface with name as "Alice" and phone as "123-456". Then create a variable contact2 of type ContactType with name as "Bob" and phone as "789-012".

Typescript

interface ContactInterface {
  name: string;
  phone: string;
}

type ContactType = {
  name: string;
  phone: string;
};

// Your code here

Hint

Use const contact1: ContactInterface = { name: "Alice", phone: "123-456" }; and similarly for contact2.

4

Print the contacts

Print contact1 and contact2 to the console using two separate console.log statements.

Typescript

interface ContactInterface {
  name: string;
  phone: string;
}

type ContactType = {
  name: string;
  phone: string;
};

const contact1: ContactInterface = { name: "Alice", phone: "123-456" };
const contact2: ContactType = { name: "Bob", phone: "789-012" };

// Your code here

Hint

Use console.log(contact1); and console.log(contact2); to show the contacts.

Practice

1. Which statement best describes when to use an interface instead of a type alias in TypeScript?

easy

A. Use interface when you want to extend or merge object shapes.

B. Use interface only for primitive types like string or number.

C. Use interface to create union or tuple types.

D. Use interface when you want to name any type, including functions.

Solution

1. Step 1: Understand interface capabilities

   Interfaces are designed to describe object shapes and support extension and merging.

2. Step 2: Compare with type alias features

   Type aliases can name any type but do not support merging and are less suited for extension of object shapes.

3. Final Answer:

   Use interface when you want to extend or merge object shapes. -> Option A

4. Quick Check:

   Interface = extension and merging [OK]

Hint: Interfaces merge and extend; type aliases do not [OK]

Common Mistakes:

• Thinking interfaces can name union types
• Believing type aliases support merging
• Using interface for primitives only

2. Which of the following is the correct syntax to declare a type alias for a union of string literals?

easy

A. interface Status = 'success' | 'error';

B. interface Status: 'success' | 'error';

C. type Status: 'success' | 'error';

D. type Status = 'success' | 'error';

Solution

1. Step 1: Recall type alias syntax

   Type aliases use the keyword type followed by the name, equals sign, and the type expression.

2. Step 2: Identify union type declaration

   The union of string literals is written as 'success' | 'error' after the equals sign.

3. Final Answer:

   type Status = 'success' | 'error'; -> Option D

4. Quick Check:

   Type alias syntax = type Name = TypeExpression [OK]

Hint: Use 'type' keyword with '=' for aliases [OK]

Common Mistakes:

• Using 'interface' for union types
• Using ':' instead of '=' in type alias
• Mixing interface and type alias syntax

3. Given the following code, what will be the output of console.log(user1.age);?

interface User {
  name: string;
}

interface User {
  age: number;
}

const user1: User = { name: 'Alice', age: 30 };

medium

A. 30

B. undefined

C. TypeScript error: Duplicate identifier 'User'

D. Runtime error

Solution

1. Step 1: Understand interface merging

   TypeScript merges multiple interface declarations with the same name into one combined interface.

2. Step 2: Check the combined interface properties

   The merged User interface has both name and age properties, so user1 can have both.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   Interface merging allows combined properties [OK]

Hint: Interfaces with same name merge properties [OK]

Common Mistakes:

• Expecting a duplicate identifier error
• Thinking type aliases merge
• Assuming age is undefined

4. Identify the error in the following code and choose the correct fix:

type Person = {
  name: string;
};

type Person = {
  age: number;
};

medium

A. Use union type instead of redeclaration.

B. Change both to interfaces to allow merging.

C. Type aliases cannot be redeclared; rename one alias.

D. No error; code is valid.

Solution

1. Step 1: Understand redeclaration rules for type aliases

   Type aliases cannot be declared multiple times with the same name; this causes a duplicate identifier error.

2. Step 2: Identify the fix

   Renaming one of the type aliases avoids the conflict; interfaces can merge but type aliases cannot.

3. Final Answer:

   Type aliases cannot be redeclared; rename one alias. -> Option C

4. Quick Check:

   Type aliases = no redeclaration [OK]

Hint: Type aliases cannot be declared twice with same name [OK]

Common Mistakes:

• Assuming type aliases merge like interfaces
• Ignoring duplicate identifier error
• Trying to redeclare type alias without rename

5. You want to create a reusable type that can represent either a user object with name and age or a string ID. Which is the best approach?

hard

A. Use an interface for the user object and a separate type alias for the union with string.

B. Use a type alias with a union of the user object type and string.

C. Use an interface with a union inside it.

D. Use two interfaces and merge them.

Solution

1. Step 1: Identify the need for union types

   You want a type that can be either an object or a string, which requires a union type.

2. Step 2: Choose the best syntax for union types

   Type aliases can represent unions directly, while interfaces cannot represent unions themselves.

3. Final Answer:

   Use a type alias with a union of the user object type and string. -> Option B

4. Quick Check:

   Type aliases = best for unions [OK]

Hint: Use type alias for unions including objects and primitives [OK]

Common Mistakes:

• Trying to use interface for union types
• Merging interfaces to represent unions
• Separating types unnecessarily