Question 1

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 exactly which access failed even when several are chained together on one line.

The underlying causes fall into a few recognisable groups.

- Data that has not arrived yet. This dominates in front-end code. A component renders before a fetch resolves, state is initially undefined, and reading a field on it throws. The value is not wrong, it is simply not there yet.
- A function that returns nothing. A missing return statement, or a return placed inside a branch that did not execute, yields undefined, and the caller then treats it as an object.
- A key that does not exist. Usually a typo, a casing mismatch, or an API response whose shape differs from what the code expects. Nested access makes this worse, since only one level needs to be missing.
- An array index that is out of range, or a find operation that matched nothing. Both produce undefined rather than throwing, so the error surfaces at the next property access instead of at the real mistake.

Optional chaining is the usual fix and short-circuits to undefined instead of throwing. It is worth being deliberate about it, though, because it silences the symptom whether or not the value was supposed to be present. If a field should always exist, an optional chain will quietly turn a loud crash into a blank screen or a silently skipped operation, which is harder to diagnose later.

A more durable approach is to handle the absent case explicitly: initialise state with a sensible empty value, guard early and return, or render a loading state while data is pending. Reserve optional chaining for values that are genuinely optional.

Question 2

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 3

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 4

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

Question 5

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.

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

Why does my Node app crash with an unhandled promise rejection?

Accepted Answer

A promise that rejects with nothing attached to handle it produces an unhandled rejection, and modern Node treats that as fatal by default. The process exits. This changed from earlier versions where

Related Questions