NonNullable type in Typescript - Step-by-Step Execution

Concept Flow - NonNullable type

Start with a type T

↓

Check each member of T

↓

Is member null or undefined?

Yes→Remove it

No↓

Keep member

↓

Result: Type without null or undefined

NonNullable removes null and undefined from a type, leaving only the usable parts.

Execution Sample

Typescript

type Example = string | number | null | undefined;
type Clean = NonNullable<Example>;

let a: Clean = "hello";
let b: Clean = 42;
// let c: Clean = null; // Error
// let d: Clean = undefined; // Error

This code removes null and undefined from Example, so Clean only allows string or number.

Execution Table

Step	Type Member	Is null or undefined?	Action	Resulting Type Members
1	string	No	Keep	string
2	number	No	Keep	string | number
3	null	Yes	Remove	string | number
4	undefined	Yes	Remove	string | number
5	End	-	-	string | number

💡 All members checked; null and undefined removed, leaving string | number

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Type Members	string | number | null | undefined	string	string | number	string | number	string | number	string | number

Key Moments - 2 Insights

Why can't we assign null or undefined to a NonNullable type variable?

Because NonNullable removes null and undefined from the type, so those values are not allowed. See execution_table rows 3 and 4 where null and undefined are removed.

Does NonNullable change the original type or create a new one?

It creates a new type without null and undefined, leaving the original type unchanged. The variable_tracker shows the transformation step by step.

Visual Quiz - 3 Questions

Look at the execution_table, what is the resulting type after step 2?

A string | number

B string

C null

D undefined

💡 Hint

Check the 'Resulting Type Members' column at step 2 in the execution_table.

At which step are null and undefined removed from the type?

A Step 1 and 2

B Step 3 and 4

C Step 5

D None

💡 Hint

Look at the 'Is null or undefined?' column in execution_table rows 3 and 4.

If the original type was only string | null, what would NonNullable<string | null> be?

A string | null

B null

C string

D string | undefined

💡 Hint

NonNullable removes null, so only string remains.

Concept Snapshot

NonNullable<T> removes null and undefined from type T.
Use it to ensure variables can't be null or undefined.
Syntax: type Clean = NonNullable<OriginalType>;
Result: Clean has only non-nullable members.
Useful for safer code and avoiding runtime errors.

Full Transcript

The NonNullable type in TypeScript takes a type T and removes null and undefined from it. This means if you have a type like string | number | null | undefined, applying NonNullable will give you string | number only. Step by step, each member is checked: if it is null or undefined, it is removed; otherwise, it is kept. This creates a new type without null or undefined. Variables of this new type cannot be assigned null or undefined values, helping prevent errors. The original type remains unchanged. This is useful when you want to be sure a value is always present and not null or undefined.

Practice

1.

What does the NonNullable type do in TypeScript?

easy

A. Converts a type to a string

B. Adds null and undefined to a type

C. Removes null and undefined from a type

D. Makes a type optional

Solution

1. Step 1: Understand the purpose of NonNullable

   The NonNullable type removes null and undefined from a given type, ensuring the value is always defined.

2. Step 2: Compare options with definition

   Only Removes null and undefined from a type correctly describes this behavior; others describe different or incorrect behaviors.

3. Final Answer:

   Removes null and undefined from a type -> Option C

4. Quick Check:

   NonNullable removes null and undefined [OK]

Hint: Remember: NonNullable cuts out null and undefined [OK]

Common Mistakes:

• Thinking it adds null or undefined
• Confusing it with making types optional
• Assuming it converts types to strings

2.

Which of the following is the correct syntax to use NonNullable on a type T?

easy

A. NonNullable(T)

B. NonNullable{T}

C. NonNullable[T]

D. NonNullable<T>

Solution

1. Step 1: Recall TypeScript generic syntax

   TypeScript uses angle brackets <> to apply generic types, like NonNullable<T>.

2. Step 2: Match options with correct syntax

   NonNullable<T> uses the correct generic syntax. Options A, C, and D use incorrect brackets or parentheses.

3. Final Answer:

   NonNullable<T> -> Option D

4. Quick Check:

   Generic types use <> brackets [OK]

Hint: Use angle brackets for generics: NonNullable<T> [OK]

Common Mistakes:

• Using parentheses instead of angle brackets
• Using square brackets or curly braces
• Confusing function call syntax with type syntax

3.

What is the type of value after this code runs?

type MaybeString = string | null | undefined;
const value: NonNullable<MaybeString> = "hello";

medium

A. string

B. null | undefined

C. string | null | undefined

D. never

Solution

1. Step 1: Understand the original type

   MaybeString can be string, null, or undefined.

2. Step 2: Apply NonNullable to remove null and undefined

   Using NonNullable<MaybeString> removes null and undefined, leaving only string.

3. Final Answer:

   string -> Option A

4. Quick Check:

   NonNullable removes null and undefined, leaving string [OK]

Hint: NonNullable removes null and undefined from union types [OK]

Common Mistakes:

• Thinking the type still includes null or undefined
• Confusing NonNullable with Partial or Required
• Assuming the type becomes never

4.

Identify the error in this code snippet:

type User = { name: string | null };
type CleanUser = NonNullable<User>;

medium

A. There is no error; code is correct

B. The syntax for NonNullable is incorrect

C. NonNullable removes null from properties inside objects automatically

D. NonNullable cannot be applied to object types directly

Solution

1. Step 1: Understand what NonNullable does

   NonNullable removes null and undefined from a type itself, not from nested properties.

2. Step 2: Analyze the code

   The code is syntactically correct. NonNullable<User> results in the same type as User since User is not a union including null or undefined at the top level.

3. Final Answer:

   There is no error; code is correct -> Option A

4. Quick Check:

   Code compiles without errors [OK]

Hint: NonNullable can be applied to object types but does not clean nested properties [OK]

Common Mistakes:

• Believing NonNullable cleans nested properties automatically
• Thinking the syntax for NonNullable is incorrect
• Thinking NonNullable cannot be applied to object types

5.

Given this type, how can you create a new type NonNullUser where the email property cannot be null or undefined using NonNullable?

type User = {
  id: number;
  email: string | null | undefined;
};

hard

A. type NonNullUser = NonNullable<User>

B. type NonNullUser = { id: number; email: NonNullable<string | null | undefined> }

C. type NonNullUser = { id: number; email: string }

D. type NonNullUser = { id: number; email: string | null }

Solution

1. Step 1: Understand the goal

   We want to keep id as is, but make email exclude null and undefined.

2. Step 2: Apply NonNullable to the email property only

   Using NonNullable<string | null | undefined> on email removes null and undefined, leaving just string.

3. Step 3: Check other options

   type NonNullUser = NonNullable<User> removes null/undefined from the whole User type, which does not affect nested properties. type NonNullUser = { id: number; email: string } changes the type but does not use NonNullable. type NonNullUser = { id: number; email: string | null } still allows null.

4. Final Answer:

   type NonNullUser = { id: number; email: NonNullable<string | null | undefined> } -> Option B

5. Quick Check:

   Apply NonNullable only to the property needing it [OK]

Hint: Use NonNullable on specific properties, not whole object [OK]

Common Mistakes:

• Applying NonNullable to the whole object type
• Not removing null and undefined from email
• Changing type without NonNullable