Course contentsShow
← JavaScript
Lesson 565 of 2,72314. The 'this' KeywordFree lesson

Binding Arrow Functions (Spoiler: It Doesn't Work)

Why call, apply, and bind have no effect on 'this' inside arrow functions.

Binding Arrow Functions (Spoiler: It Doesn't Work)

You'll learn why call(), apply(), and bind() have absolutely no effect on this inside arrow functions.

The Core Idea

Arrow functions use lexical binding for this — they capture this from their surrounding scope at the moment they're defined. This binding is permanent and unchangeable. When you try to use call(), apply(), or bind() on an arrow function, JavaScript politely ignores your attempt. The arrow function keeps using its original lexical this no matter what.

Why This Happens

Remember that arrow functions deliberately break the four dynamic binding rules. They don't have their own this at all — they inherit it from the enclosing scope. Since they don't participate in dynamic binding, the manual binding methods can't override something that was never dynamically bound in the first place.

Think of it like this: Regular functions are like rental cars — you can reassign who's driving with call(), apply(), or bind(). Arrow functions are like trains on fixed tracks — they already know their route (lexical this), and no amount of steering wheel turning will change their path.

What Actually Happens

const obj = {
  value: 42,
  arrow: () => {
    console.log(this.value);
  }
};

const other = { value: 99 };

// These all fail to change 'this':
obj.arrow.call(other);    // undefined (or global value)
obj.arrow.apply(other);   // undefined (or global value)
const bound = obj.arrow.bind(other);
bound();                  // undefined (or global value)

The arrow function's this was captured when it was created, and no binding method can override it.

Key Takeaway: Arrow functions ignore call(), apply(), and bind() because their this is lexically bound at creation time, not dynamically bound at call time — making manual binding methods powerless.