Class checking: "instanceof"

The instanceof operator allows to check whether an object belongs to a certain class. It also takes inheritance into account. Such a check may be necessary in many cases. For example, it can be used for building a polymorphic function, the one that treats arguments differently depending on their type.

The instanceof operator [#ref-instanceof]

The syntax is: It returns true if obj belongs to the Class or a class inheriting from it. For instance: It also works with constructor functions: …And with built-in classes like Array: Please note that arr also belongs to the Object class. That’s because Array prototypically inherits from Object. Normally, instanceof examines the prototype chain for the check. We can also set a custom logic in the static method Symbol.hasInstance. The algorithm of obj instanceof Class works roughly as follows: 1. If there’s a static method Symbol.hasInstance, then just call it: ClassSymbol.hasInstance. It should return either true or false, and we’re done. That’s how we can customize the behavior of instanceof. For example:

// set up instanceof check that assumes that
// anything with canEat property is an animal
class Animal {
static Symbol.hasInstance {
if (obj.canEat) return true;
let obj = { canEat: true };
alert(obj instanceof Animal); // true: AnimalSymbol.hasInstance is called

1. Most classes do not have Symbol.hasInstance. In that case, the standard logic is used: obj instanceof Class checks whether Class.prototype is equal to one of the prototypes in the obj prototype chain. In other words, compare one after another:

obj.__proto__ === Class.prototype?
obj.__proto__.__proto__ === Class.prototype?
obj.__proto__.__proto__.__proto__ === Class.prototype?
...
// if any answer is true, return true
// otherwise, if we reached the end of the chain, return false

In the example above rabbit.proto === Rabbit.prototype, so that gives the answer immediately. In the case of an inheritance, the match will be at the second step:

class Animal {}
class Rabbit extends Animal {}
let rabbit = new Rabbit();
alert(rabbit instanceof Animal); // true
// rabbit.__proto__ === Animal.prototype (no match)
// rabbit.__proto__.__proto__ === Animal.prototype (match!)

Here’s the illustration of what rabbit instanceof Animal compares with Animal.prototype: By the way, there’s also a method objA.isPrototypeOf(objB), that returns true if objA is somewhere in the chain of prototypes for objB. So the test of obj instanceof Class can be rephrased as Class.prototype.isPrototypeOf(obj). It’s funny, but the Class constructor itself does not participate in the check! Only the chain of prototypes and Class.prototype matters. That can lead to interesting consequences when a prototype property is changed after the object is created. Like here:

Bonus: Object.prototype.toString for the type

We already know that plain objects are converted to string as [object Object]: That’s their implementation of toString. But there’s a hidden feature that makes toString actually much more powerful than that. We can use it as an extended typeof and an alternative for instanceof. Sounds strange? Indeed. Let’s demystify. By specification, the built-in toString can be extracted from the object and executed in the context of any other value. And its result depends on that value. - For a number, it will be [object Number] - For a boolean, it will be [object Boolean] - For null: [object Null] - For undefined: [object Undefined] - For arrays: [object Array] - …etc (customizable). Let’s demonstrate: Here we used call as described in the chapter to execute the function objectToString in the context this=arr. Internally, the toString algorithm examines this and returns the corresponding result. More examples:

Symbol.toStringTag

The behavior of Object toString can be customized using a special object property Symbol.toStringTag. For instance: For most environment-specific objects, there is such a property. Here are some browser specific examples: As you can see, the result is exactly Symbol.toStringTag (if exists), wrapped into [object …]. At the end we have “typeof on steroids” that not only works for primitive data types, but also for built-in objects and even can be customized. We can use {}.toString.call instead of instanceof for built-in objects when we want to get the type as a string rather than just to check.

Summary

Let’s summarize the type-checking methods that we know: As we can see, {}.toString is technically a “more advanced” typeof. And instanceof operator really shines when we are working with a class hierarchy and want to check for the class taking into account inheritance.

class Rabbit {}
let rabbit = new Rabbit();

// is it an object of Rabbit class?
*!*
alert( rabbit instanceof Rabbit ); // true
*/!*