TypeScript `asserts` and Type Predicates in 2026: Writing Guards That Actually Narrow Correctly

TypeScript's type system relies heavily on guards to ensure that runtime values conform to expected types. These guards come in two primary forms: type predicates and assertion functions. The distinction between these two is crucial for writing guards that actually narrow types correctly. Type predicates, denoted by `value is Type`, return a boolean value and enable conditional narrowing.

When the predicate returns `true`, TypeScript narrows the type of the input parameter to the specified type within the scope where the guard is evaluated. This mechanism allows developers to write more precise and safe code. On the other hand, assertion functions, denoted by `asserts value is Type`, do not return a value but instead throw an error if the condition is not met.

This unconditional narrowing ensures that the type safety is enforced throughout the remainder of the scope where the guard is used. The key takeaway from this article is that developers often mistakenly use boolean-returning functions as type predicates, which leads to validation theater—code that performs checks but does not genuinely narrow types.

To avoid this pitfall, it is essential to use the appropriate syntax (`value is Type` for predicates and `asserts value is Type` for assertions) based on whether the guard should return a boolean or throw an error. This distinction is particularly important in handling runtime validation, where failing to narrow types correctly can result in silent bugs that only surface in production.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.