Question 1

Why does this become undefined inside a callback in JavaScript?

Accepted Answer

In JavaScript the value of this is determined by how a function is called, not by where it was written. When you pass a method somewhere as a callback, you pass the function itself and leave the object behind. Whatever later invokes it does so without an owner, so this is not the object you expected. In strict mode, which modules use by default, that means undefined rather than the global object, which is why the failure surfaces as a property access on undefined.

The classic version is extracting a method and handing it to an event listener or a timer. The method body is unchanged, but the call site has changed, and that is what matters.

There are three standard fixes.

1. Use an arrow function. Arrow functions have no binding of their own and close over the surrounding scope, so the value is fixed at definition rather than at call time. Defining class methods as arrow-function properties makes them safe to pass around.
2. Bind explicitly. Creating a bound copy permanently attaches the receiver, commonly done in a constructor in older codebases.
3. Wrap the call. Passing a small arrow function that calls the method on the object preserves the receiver, because the call still goes through the object.

The consequence of arrow functions having no binding is that they are the wrong choice in a few places. An arrow function used as an object literal method will not see the object, and one used as a constructor or as a traditional event handler expecting the element as its receiver will not behave as intended.

Modern code largely sidesteps the whole area by preferring arrow functions and avoiding the keyword outside classes, which removes an entire category of confusion.

Question 2

What causes Cannot read properties of undefined in JavaScript?

Accepted Answer

The error means you accessed a property on a value that was undefined or null. Modern engines name the property in the message, and that name is the most useful clue available, because it tells you

Question 3

What are scope and closures?

Accepted Answer

Scope determines where a name is visible. A closure is what happens when a function keeps access to its scope after that scope would otherwise be gone. The second is the one that confuses people, and

Question 4

Why does TypeScript say Object is possibly undefined?

Accepted Answer

The compiler is telling you that a value type includes undefined and you are using it as though it does not. With strict null checking enabled, undefined and null are not silently assignable to other

Question 5

What is the difference between null and undefined in JavaScript?

Accepted Answer

Undefined means a value was never assigned. Null means a value was deliberately set to nothing. The language draws that distinction, and whether your code should is a style decision worth making

Question 6

Why does my async function return a Promise instead of a value?

Accepted Answer

This is the defining behaviour of async functions rather than a mistake. Declaring a function async wraps its return value in a promise automatically. Returning a number from an async function

Question 7

Should errors be exceptions or return values?

Accepted Answer

A genuine design disagreement rather than a settled question — and the honest answer is that the two approaches differ in what they make visible in the type system and what they make easy to ignore.

Related Questions