Why instanceof fails on interfaces in Typescript - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does instanceof fail with interfaces in TypeScript?

Consider the following TypeScript code snippet:

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

What will be the output and why?

A TypeError, because pet is not a class instance

B false, because interfaces do not exist at runtime and instanceof checks the prototype chain

C SyntaxError, because instanceof cannot be used with interfaces

D true, because pet is an instance of a class that implements Animal

💡 Hint

Think about what instanceof checks at runtime and what interfaces represent in TypeScript.

The instanceof operator checks if an object has a certain constructor in its prototype chain at runtime. Interfaces in TypeScript are only used at compile time for type checking and do not exist in the generated JavaScript code. Therefore, instanceof cannot be used with interfaces and will always return false.

❓ Predict Output

intermediate

Output of instanceof with class and interface

What is the output of this TypeScript code?

interface Vehicle { wheels: number; }
class Car implements Vehicle { wheels = 4; }
const myCar = new Car();
console.log(myCar instanceof Car);
console.log(myCar instanceof Vehicle);

A

true
false

B

true
true

C

false
false

D

false
true

💡 Hint

Remember that interfaces do not exist at runtime.

myCar instanceof Car returns true because myCar is created from the Car class. However, myCar instanceof Vehicle returns false because Vehicle is an interface and does not exist at runtime.

🔧 Debug

advanced

Why does this instanceof check always fail?

Look at this TypeScript code:

interface Shape { area(): number; }
class Circle implements Shape {
  radius: number;
  constructor(radius: number) { this.radius = radius; }
  area() { return Math.PI * this.radius * this.radius; }
}
const shape: Shape = new Circle(5);
if (shape instanceof Shape) {
  console.log('It is a Shape');
} else {
  console.log('Not a Shape');
}

Why does it always print 'Not a Shape'?

A Because Shape is an interface and does not exist at runtime, so instanceof always fails

B Because Circle does not extend Shape class, so instanceof returns false

C Because area method is missing in the object

D Because shape is not an object

💡 Hint

Think about what instanceof checks and what interfaces represent.

instanceof checks the prototype chain for a constructor function. Interfaces are only a compile-time construct and do not exist in the JavaScript output, so instanceof Shape always returns false.

📝 Syntax

advanced

Which code snippet causes a runtime error due to instanceof misuse?

Which of the following TypeScript code snippets will cause a runtime error when executed?

A

interface Person { name: string; }
const p: Person = { name: 'Alice' };
console.log(p instanceof Person);

B

class Person { name: string; constructor(name: string) { this.name = name; } }
const p = new Person('Alice');
console.log(p instanceof Person);

C

const p = { name: 'Alice' };
console.log(p instanceof Object);

D

const p = null;
console.log(p instanceof Object);

💡 Hint

Consider what values can be used with instanceof without causing errors.

Using instanceof with null causes a runtime TypeError because null is not an object and cannot have a prototype chain.

🚀 Application

expert

How to check if an object implements an interface at runtime?

Since instanceof does not work with interfaces in TypeScript, which approach below correctly checks if an object implements the Logger interface at runtime?

interface Logger { log(message: string): void; }

A Use <code>typeof obj === 'Logger'</code> to check the type

B Use <code>obj instanceof Logger</code> to check if it implements Logger

C Use <code>if ('log' in obj && typeof obj.log === 'function')</code> to check for the method

D Use <code>obj.constructor.name === 'Logger'</code> to check the class name

💡 Hint

Interfaces do not exist at runtime, so you must check properties manually.

Because interfaces are erased during compilation, you cannot use instanceof or typeof to check for them. Instead, checking if the object has the required method with the correct type is the common runtime approach.

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