Why `str.length` Works on a Primitive: V8's Prototype Wrapper Trick

For Western developers working in JavaScript, this explains a fundamental and often confusing behavior: why primitives have methods. Understanding V8's temporary wrapper objects and prototype chain resolution is essential for debugging property lookups, writing performant code, and avoiding subtle bugs when working with strings, numbers, and booleans.

JavaScript developers know that primitives like strings can't hold custom properties. Yet `str.length` works. The answer lies in V8's internal handling: every primitive literal is temporarily promoted to an object via its corresponding constructor — `new String('abc')` — then demoted back to a primitive before output. During that brief object life, the prototype chain is linked, so properties like `.length` are inherited from `String.prototype`.

This article walks through the three ways to create objects in JavaScript — object literals, native constructors, and custom constructors with `new` — and then dissects what `new` actually does: create an empty `this` object, execute the constructor's code, and link `this.__proto__` to the constructor's `prototype`. For primitives, V8 performs an extra cleanup step, deleting any custom properties added to the wrapper object, but the prototype link remains, enabling method access.

The practical takeaway is that JavaScript's "everything is an object" mantra is more than philosophy — it's a concrete engine behavior. Understanding the prototype chain and the temporary wrapper object explains why primitives have methods, why `const` objects can be mutated, and how to override prototype properties if you really want to.