Interface vs type alias decision in Typescript

Introduction

Interfaces and type aliases both describe shapes of data in TypeScript. Choosing between them helps keep your code clear and easy to work with.

When you want to describe the shape of an object that might be extended later.

When you need to create a union or intersection of types.

When you want to define a simple alias for a type like a string or number.

When you want to use declaration merging to add properties later.

When you want to describe complex types like tuples or mapped types.

Syntax

Typescript

interface InterfaceName {
  propertyName: type;
}

type TypeAliasName = typeExpression;

Interfaces describe object shapes and can be extended or merged.

Type aliases can name any type, including primitives, unions, and tuples.

Examples

This interface describes an object with a name and age.

Typescript

interface Person {
  name: string;
  age: number;
}

This type alias defines ID as either a string or a number.

Typescript

type ID = string | number;

Interfaces can extend other interfaces to add more properties.

Typescript

interface Animal {
  species: string;
}

interface Dog extends Animal {
  breed: string;
}

This type alias defines a tuple for coordinates with two numbers.

Typescript

type Coordinates = [number, number];

Sample Program

This program shows how to create an interface and a type alias with the same shape, then use them to type objects.

Typescript

interface User {
  id: number;
  name: string;
}

type UserAlias = {
  id: number;
  name: string;
};

const user1: User = { id: 1, name: "Alice" };
const user2: UserAlias = { id: 2, name: "Bob" };

console.log(user1);
console.log(user2);

Important Notes

Interfaces support declaration merging, so you can add properties later by declaring the same interface again.

Type aliases cannot be reopened once declared.

Use interfaces for objects you expect to extend or implement in classes.

Summary

Interfaces are best for describing object shapes and can be extended or merged.

Type aliases can name any type, including unions and tuples, but cannot be merged.

Choose based on whether you need extension, merging, or complex type expressions.

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