One TypeScript behavior that confused me for a long time was this: const values = [ 1 , 2 , undefined , 4 ]. filter ( Boolean ); values . map (( v ) => v * 2 ); Enter fullscreen mode Exit fullscreen mode At runtime, this works perfectly. But TypeScript may still complain: 'v' is possibly 'undefined' Enter fullscreen mode Exit fullscreen mode At first glance, this feels wrong. We already filtered the array. Why is TypeScript still acting like undefined can exist? The Important Thing to Understand TypeScript does not deeply analyze what Boolean() actually does. Instead, TypeScript mostly relies on: control-flow analysis recognized syntax patterns explicit type predicates So when you write: . filter ( Boolean ) Enter fullscreen mode Exit fullscreen mode TypeScript mainly sees: "A function returning boolean" Enter fullscreen mode Exit fullscreen mode not: "This removes undefined and null values from the array" Enter fullscreen mode Exit fullscreen mode That relationship gets lost.…