Why instanceof fails on interfaces in Typescript - See It in Action

Why instanceof Fails on Interfaces

📖 Scenario: Imagine you are building a simple app where you want to check if an object follows a certain shape (interface) before using it.

🎯 Goal: You will learn why the instanceof operator does not work with interfaces in TypeScript and how to check object types safely.

📋 What You'll Learn

Create an interface called Person with properties name and age

Create a class called Employee that implements Person

Create an object of type Employee

Try to use instanceof Person and see why it fails

Use a type guard function to check if an object matches the Person interface

💡 Why This Matters

🌍 Real World

When working with TypeScript, you often want to check if objects have certain shapes before using them safely.

💼 Career

Understanding how to check types correctly helps prevent bugs and is important for writing reliable TypeScript code in professional projects.

1

Create the Person interface and Employee class

Create an interface called Person with properties name (string) and age (number). Then create a class called Employee that implements Person and has a constructor to set name and age.

Typescript

// Your code here

Hint

Interfaces define a shape but do not exist at runtime. Classes create real objects you can check with instanceof.

2

Create an Employee object

Create a variable called emp and assign it a new Employee object with name as "Alice" and age as 30.

Typescript

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

class Employee implements Person {
    constructor(public name: string, public age: number) {}
}

// Your code here

Hint

Use the new keyword to create an instance of the class.

3

Try using instanceof with the interface

Write an if statement that checks if emp instanceof Person and inside it, write console.log("emp is a Person"). Also add an else block with console.log("emp is NOT a Person").

Typescript

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

class Employee implements Person {
    constructor(public name: string, public age: number) {}
}

const emp = new Employee("Alice", 30);

// Your code here

Hint

Interfaces do not exist at runtime, so instanceof cannot check them.

4

Use a type guard function to check the interface

Create a function called isPerson that takes obj: any and returns obj is Person. Inside, check if obj has name and age properties with correct types. Then use if (isPerson(emp)) to print "emp is a Person", else print "emp is NOT a Person".

Typescript

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

class Employee implements Person {
    constructor(public name: string, public age: number) {}
}

const emp = new Employee("Alice", 30);

if (emp instanceof Person) {
    console.log("emp is a Person");
} else {
    console.log("emp is NOT a Person");
}

// Your code here

Hint

Type guard functions check properties manually because interfaces vanish after compiling.

Practice

1. Why does the instanceof operator fail when used to check if an object implements a TypeScript interface?

easy

A. Because interfaces are only used for styling in TypeScript.

B. Because instanceof only works with primitive types.

C. Because interfaces do not exist at runtime in JavaScript.

D. Because instanceof requires a function as the right operand.

Solution

1. Step 1: Understand what instanceof checks

   The instanceof operator checks if an object was created from a specific class or constructor function at runtime.

2. Step 2: Recognize interface behavior in TypeScript

   Interfaces in TypeScript are only used during compilation and do not exist in the generated JavaScript code, so instanceof cannot check them.

3. Final Answer:

   Because interfaces do not exist at runtime in JavaScript. -> Option C

4. Quick Check:

   Interfaces disappear at runtime = A [OK]

Hint: Remember: interfaces vanish after compile, so instanceof fails [OK]

Common Mistakes:

• Thinking instanceof works with interfaces
• Confusing interfaces with classes
• Assuming interfaces exist at runtime
• Using instanceof with primitives

2. Which of the following is the correct syntax to check if an object is an instance of a class Person in TypeScript?

easy

A. if (obj instanceof Person) { }

B. if (obj instanceof 'Person') { }

C. if (obj instanceof InterfacePerson) { }

D. if (obj instanceof { name: string }) { }

Solution

1. Step 1: Recall instanceof syntax

   The right side of instanceof must be a class or constructor function, not a string or interface.

2. Step 2: Identify valid usage

   Only obj instanceof Person is valid syntax to check if obj is created from class Person.

3. Final Answer:

   if (obj instanceof Person) { } -> Option A

4. Quick Check:

   Right operand must be class/constructor = C [OK]

Hint: Use class name without quotes for instanceof [OK]

Common Mistakes:

• Using interface names with instanceof
• Putting class name in quotes
• Using object literals on right side
• Confusing type and value syntax

3. Consider this TypeScript code:

interface Animal { name: string }
class Dog implements Animal { constructor(public name: string) {} }
const pet = new Dog('Buddy');
console.log(pet instanceof Dog);
console.log(pet instanceof Animal);

What is the output?

medium

A. false\nfalse

B. true\ntrue

C. false\ntrue

D. true\nfalse

Solution

1. Step 1: Check pet instanceof Dog

   Since pet was created with new Dog(), this returns true.

2. Step 2: Check pet instanceof Animal

   Animal is an interface and does not exist at runtime, so this returns false.

3. Final Answer:

   true\nfalse -> Option D

4. Quick Check:

   Class instance true, interface instance false = A [OK]

Hint: Only classes work with instanceof, interfaces do not [OK]

Common Mistakes:

• Expecting interface check to return true
• Confusing interface with class
• Assuming interfaces exist at runtime
• Misreading output order

4. Given this code snippet:

interface Vehicle { wheels: number }
function isVehicle(obj: any) {
  return obj instanceof Vehicle;
}

Why does this code cause an error or unexpected behavior?

medium

A. Because Vehicle is an interface and cannot be used with instanceof.

B. Because obj is not typed correctly.

C. Because instanceof requires a string argument.

D. Because Vehicle is not imported.

Solution

1. Step 1: Identify the use of instanceof with interface

   The code uses instanceof with Vehicle, which is an interface.

2. Step 2: Understand interface runtime behavior

   Interfaces do not exist at runtime, so instanceof Vehicle is invalid and causes an error or always returns false.

3. Final Answer:

   Because Vehicle is an interface and cannot be used with instanceof. -> Option A

4. Quick Check:

   Interfaces can't be checked with instanceof = D [OK]

Hint: Never use instanceof with interfaces, only classes [OK]

Common Mistakes:

• Trying to check interfaces with instanceof
• Ignoring runtime absence of interfaces
• Assuming instanceof works with types
• Misunderstanding error cause

5. You want to check at runtime if an object matches the shape of an interface Person { name: string; age: number; }. Since instanceof does not work with interfaces, which approach is best?

hard

A. Use instanceof Person anyway; it will work after compilation.

B. Manually check if object has required properties with correct types.

C. Convert the interface to a class and use instanceof.

D. Use typeof obj === 'Person' to check the type.

Solution

1. Step 1: Understand interface runtime absence

   Interfaces do not exist at runtime, so instanceof or typeof cannot check them directly.

2. Step 2: Choose property checks for runtime validation

   The best way is to manually check if the object has the required properties with the expected types.

3. Final Answer:

   Manually check if object has required properties with correct types. -> Option B

4. Quick Check:

   Manual property checks replace instanceof for interfaces = B [OK]

Hint: Check properties manually to mimic interface checks at runtime [OK]

Common Mistakes:

• Using instanceof with interfaces
• Assuming typeof works for interfaces
• Converting interfaces to classes unnecessarily
• Ignoring runtime type checks