How is the value of `this` determined?

Question

IT Interview Practice · Accepted Answer

`this` is decided by **how a function is CALLED**, not where it's defined. There are five rules:

```js
const obj = {
  x: 1,
  getX() { return this.x; },
};

obj.getX();          // 1   → method call: `this` is `obj`
const f = obj.getX;
f();                  // undefined (or window) → plain call: `this` is global/undefined
f.call(obj);          // 1   → explicit binding with call/apply/bind
new SomeClass();      //     → `this` is the brand-new instance
```

## The arrow-function exception (the important one)

Arrow functions have **no own `this`** — they inherit it from the enclosing scope at definition time. This is why arrows are perfect for callbacks:

```js
const obj = {
  items: [1, 2],
  logAll() {
    // ✅ arrow inherits `this` from logAll → `this` is obj
    this.items.forEach(i => console.log(this.items, i));

// ❌ a regular function here would have its own `this` (undefined) → crash
    // this.items.forEach(function (i) { console.log(this.items); });
  },
};
```

## The common trap

Passing a method as a callback **loses** its binding, because it's then called plainly:

```js
button.addEventListener("click", obj.getX);        // ❌ `this` is the button
button.addEventListener("click", () => obj.getX()); // ✅ keeps obj
button.addEventListener("click", obj.getX.bind(obj)); // ✅ also fine
```

## Why it matters

Misunderstanding `this` is one of the most common JS bugs.

The fix is usually an arrow function or `.bind()` to lock the intended `this`.

The arrow-function exception (the important one)

The common trap

Why it matters

Related questions