A type predicate is a special function return type that acts as a user-defined type guard, allowing you to create custom logic for narrowing types. It uses the syntax parameter is Type to tell TypeScript that if the function returns true, the parameter should be treated as the specified type.
Type predicates solve a key limitation with regular boolean functions. (A boolean function is simply a function that returns either true or false.)
Let’s break this down using an example.
Below, we have two functions:
isPerson: A helper function that checks if an age property is present inside the item and returns true or false accordingly.
processItem: Processes an item that could be either a Person or a Product. Inside, we use isPerson to narrow the item's type.
TypeScript
1
interface
interfacePerson
Person {
2
Person.name: string
name:string;
3
Person.age: number
age:number;
4
}
5
6
interface
interfaceProduct
Product {
7
Product.name: string
name:string;
8
Product.price: number
price:number;
9
}
10
11
type
typePersonOrProduct=Person|Product
PersonOrProduct=
interfacePerson
Person|
interfaceProduct
Product;
12
13
function
functionisPerson(item:PersonOrProduct):boolean
isPerson(
item: PersonOrProduct
item:
typePersonOrProduct=Person|Product
PersonOrProduct):boolean {
14
return"age"in
item: PersonOrProduct
item;
15
}
16
17
function
functionprocessItem(item:PersonOrProduct):void
processItem(
item: PersonOrProduct
item:
typePersonOrProduct=Person|Product
PersonOrProduct) {
18
if (
functionisPerson(item:PersonOrProduct):boolean
isPerson(
item: PersonOrProduct
item)) {
19
var console:Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:
A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.
Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(newError('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
// Error: Whoops, something bad happened
// at [eval]:5:15
// at Script.runInThisContext (node:vm:132:18)
// at Object.runInThisContext (node:vm:309:38)
// at node:internal/process/execution:77:19
// at [eval]-wrapper:6:22
// at evalScript (node:internal/process/execution:76:60)
// at node:internal/main/eval_string:23:3
constname='Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
constout=getStreamSomehow();
consterr=getStreamSomehow();
constmyConsole=new console.Console(out, err);
myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(newError('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).
Error ts(2339) ― Property 'age' does not exist on type 'PersonOrProduct'.
Property 'age' does not exist on type 'Product'.
20
}
21
}
This code produces an error, but why? The logic inside isPerson is perfectly sound.
The problem is that to the TypeScript compiler, the isPerson function is a "black box." It knows the function takes a PersonOrProduct and returns a boolean, but it has no idea that the true or false value is related to the type of item.
So, even inside the if (isPerson(item)) block, TypeScript's understanding of the item variable has not changed. It still thinks item is a PersonOrProduct, and it correctly points out that you can't safely access .age on a PersonOrProduct.
So, how do we fix this?
This is exactly the problem that type predicates are designed to solve.
We fix it by changing only the return type of our isPerson function:
// AT COMPILE-TIME, TypeScript sees this `if` block.
4
// It says: "The developer used a function with the promise `item is Person`.
5
// Since I'm inside the 'true' part of the `if` statement,
6
// I will honor that promise and treat `item` as a `Person` here."
7
var console:Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:
A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.
Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(newError('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
// Error: Whoops, something bad happened
// at [eval]:5:15
// at Script.runInThisContext (node:vm:132:18)
// at Object.runInThisContext (node:vm:309:38)
// at node:internal/process/execution:77:19
// at [eval]-wrapper:6:22
// at evalScript (node:internal/process/execution:76:60)
// at node:internal/main/eval_string:23:3
constname='Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
constout=getStreamSomehow();
consterr=getStreamSomehow();
constmyConsole=new console.Console(out, err);
myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(newError('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).
// TypeScript also says: "If the promise was not fulfilled (the function
10
// returned false), then `item` cannot be a `Person`.
11
// Since the original type was `Person | Product`, it must be a `Product`."
12
var console:Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:
A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.
Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(newError('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
// Error: Whoops, something bad happened
// at [eval]:5:15
// at Script.runInThisContext (node:vm:132:18)
// at Object.runInThisContext (node:vm:309:38)
// at node:internal/process/execution:77:19
// at [eval]-wrapper:6:22
// at evalScript (node:internal/process/execution:76:60)
// at node:internal/main/eval_string:23:3
constname='Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
constout=getStreamSomehow();
consterr=getStreamSomehow();
constmyConsole=new console.Console(out, err);
myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(newError('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).