Bird
Raised Fist0
Typescriptprogramming~5 mins

Why instanceof fails on interfaces in Typescript

Choose your learning style10 modes available
Introduction

The instanceof operator checks if an object is created from a specific class, but interfaces do not exist in the final JavaScript code. So, instanceof cannot check interfaces.

You want to check if an object is made from a certain class.
You want to avoid runtime errors by verifying object types.
You want to understand why <code>instanceof</code> does not work with interfaces.
Syntax
Typescript
object instanceof ClassName

instanceof works only with classes or constructor functions.

Interfaces are only used by TypeScript during development and disappear after compiling.

Examples
This checks if pet is created from the Dog class.
Typescript
class Dog {}
const pet = new Dog();
console.log(pet instanceof Dog); // true
This shows that instanceof cannot be used with interfaces because they do not exist at runtime.
Typescript
interface Animal {
  name: string;
}
const pet = { name: 'Buddy' };
// console.log(pet instanceof Animal); // Error: 'Animal' only exists in type space
Sample Program

This program shows that instanceof works with the Dog class but not with the Animal interface.

Typescript
interface Animal {
  name: string;
}

class Dog implements Animal {
  constructor(public name: string) {}
}

const pet = new Dog('Buddy');

console.log(pet instanceof Dog); // true

// The following line would cause an error if uncommented:
// console.log(pet instanceof Animal);
OutputSuccess
Important Notes

Interfaces are only for TypeScript's type checking and do not exist in the JavaScript output.

To check if an object matches an interface, check for the presence of required properties instead.

Use instanceof only with classes or constructor functions.

Summary

instanceof checks if an object is created from a class, not if it matches an interface.

Interfaces disappear after TypeScript compiles to JavaScript, so instanceof cannot see them.

To check interface-like shapes at runtime, check object properties manually.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard