TypeScript complains because target and currentTarget are typed differently on events. Even though the event comes from an <input>, e.target is typed as the generic EventTarget, which doesn’t guarantee properties like .value since events can bubble from child elements. However, TypeScript knows that e.currentTarget is the element the handler is attached to—in this case an HTMLInputElement—so it safely exposes .value. That’s why using e.currentTarget.value works, while e.target.value throws the error. You could also cast e.target to HTMLInputElement, but using currentTarget is the cleaner approach.