Using a juggling-check, you can test both null and undefined in one hit:
if (x == null) {
If you use a strict-check, it will only be true for values set to null and won't evaluate as true for undefined variables:
if (x === null) {
You can try this with various values using this example:
var a: number;
var b: number = null;
function check(x, name) {
if (x == null) {
console.log(name + ' == null');
}
if (x === null) {
console.log(name + ' === null');
}
if (typeof x === 'undefined') {
console.log(name + ' is undefined');
}
}
check(a, 'a');
check(b, 'b');
Output
Answer from Fenton on Stack Overflow"a == null"
"a is undefined"
"b == null"
"b === null"
Top answer 1 of 16
705
Using a juggling-check, you can test both null and undefined in one hit:
if (x == null) {
If you use a strict-check, it will only be true for values set to null and won't evaluate as true for undefined variables:
if (x === null) {
You can try this with various values using this example:
var a: number;
var b: number = null;
function check(x, name) {
if (x == null) {
console.log(name + ' == null');
}
if (x === null) {
console.log(name + ' === null');
}
if (typeof x === 'undefined') {
console.log(name + ' is undefined');
}
}
check(a, 'a');
check(b, 'b');
Output
"a == null"
"a is undefined"
"b == null"
"b === null"
2 of 16
482
if( value ) {
}
will evaluate to true if value is not:
nullundefinedNaN- empty string
'' 0false
typescript includes javascript rules.
W3Schools
w3schools.com › typescript › typescript_null.php
TypeScript Null & Undefined
TypeScript has a powerful system to deal with null or undefined values.
Is Null Checking Necessary in TypeScript for Runtime Safety?
Is your program going to work with a null value in that spot? <- focus on this More on reddit.com
22
9
August 13, 2024Object is possibly 'null' after null check.
const [map, setMap] = React.useState(null) ^ Here's the problem. Typescript is inferring the type of map here as null. i.e. it doesn't think map will every be anything other than null. You need to explicitly set map's type. Try something like this const [map, setMap] = React.useState(null) More on reddit.com
21
5
December 3, 2020return null ?
For the first part: ngOnInit is not returning null, the arrow function passwordMatcher, which I assume is a form validator, is returning null. I personally prefer to put my validators in a separate function in a separate file, but both are fine. Angular form validators are expected to return null when no errors are found. Apart from that, the formControlNames might be a bit messed up newPassword => email and newPasswordRepeat => confirm. That looks like some ugly copy / paste. So something like: export function generateMatcherValidator(newControlKey: string, confirmControlKey: string) { return (control: AbstractControl): { [key: string]: boolean } => { const newControl = control.get(newControlKey); const confirmControl = control.get(confirmControlKey); if (!newControl || !confirmControl) { return null; } return newControl.value === confirmControl.value ? null : { nomatch: true }; }; } For the second part: I quite often just do a truthy check. Although I do try to keep my code as flat as possible, so instead of wrapping entire functions in an if-condition, I just return if that condition is false. So something like: function randomFunction(someArgumentUsedToCallAfunction) { if (!someArgumentUsedToCallAfunction) { return; } do stuff, because we were called with a value } More on reddit.com
10
5
December 20, 2020returning null vs throw error ? (+ some question about refactoring)
For the first one, depends. I prefer to throw, as it may not exist or a db reading error may happen, so throwing allows to describe what happened. Just a string as the error can do the job for simple applications, but may be a good idea to have an Error class/interface for it, so you can use error codes etc. There is the Left/Right pattern from the Functional Programming. I never used it and I personally think it's ugly, but you may like it, so do your research. More on reddit.com
12
7
February 22, 2022Videos
TypeScript
typescriptlang.org › docs › handbook › release-notes › typescript-2-0.html
TypeScript: Documentation - TypeScript 2.0
In practical terms, strict null checking mode requires that all files in a compilation are null- and undefined-aware. TypeScript 2.0 implements a control flow-based type analysis for local variables and parameters.
GeeksforGeeks
geeksforgeeks.org › typescript › how-to-check-null-and-undefined-in-typescript
How to check null and undefined in TypeScript ? - GeeksforGeeks
July 23, 2025 - We can use typeof or '==' or '===' to check if a variable is null or undefined in typescript.
Omarileon
omarileon.me › blog › typescript-null-undefined
mari. | How to Detect Null and Undefined in Your TypeScript Code
February 27, 2024 - Another way to check for null or undefined is to use the nullish coalescing operator (??), which was introduced in TypeScript 3.7. If the left-hand side of the operation is non-null it returns that, otherwise it returns the right-hand side otherwise.
Reddit
reddit.com › r/reactjs › is null checking necessary in typescript for runtime safety?
r/reactjs on Reddit: Is Null Checking Necessary in TypeScript for Runtime Safety?
August 13, 2024 -
TypeScript types are only enforced at compile time and do not exist at runtime. Given this, if I define a TypeScript function that accepts a string parameter, is it necessary to perform null checks? This question arises because if the API returns null, it could lead to runtime errors.
Consider the following code snippet:
const capitalise = (val: string) => {
// Question: Is this check redundant due to TypeScript's type checking?
if (!val) {
return '';
}
return val.toUpperCase();
};
// Assume 'name' is fetched from an API or another source that could return null
const name: string = /* fetch from API or another source */;
capitalise(name);What are the best practices in such scenarios to ensure runtime safety in TypeScript applications?
Top answer 1 of 9
35
Is your program going to work with a null value in that spot? <- focus on this
2 of 9
3
I would say that the type-checking isn't necessary in the capitalise function. It might in fact make it harder to discover the error later. I would suggest that the best course of action would be to perform a null check on all the values that can't be null on the data received after doing the API-call. Assuming the API-call is its own function (which is should be), as a part of that function, check each field in the data received for null or undefined values where you don't want a null or undefined value. If one is found, either throw an error or revert to default values ('' for string, -1 for int, and so on)
TypeScript
typescriptlang.org › tsconfig › strictNullChecks.html
TypeScript: TSConfig Option: strictNullChecks
When strictNullChecks is true, null and undefined have their own distinct types and you’ll get a type error if you try to use them where a concrete value is expected. For example with this TypeScript code, users.find has no guarantee that it will actually find a user, but you can write code ...
Rampatra
blog.rampatra.com › null-vs-undefined-in-typescript-or-javascript-how-to-check-for-both-at-once
!== null vs !== undefined in Typescript or Javascript, how to check for both at once?
November 14, 2024 - Use != null only when you explicitly want to check for both null and undefined. ... If offerPrice might explicitly be null, you should use offerPrice != null to handle both cases. Take your presentation to the next level. ... Put your face and name on your screen. ... Show keypresses on your screen. ... Your to-dos on your menu bar. ... Fill forms using your right-click menu. ... Preview your Mac app icons. ... question typescript ...
TutorialsPoint
tutorialspoint.com › javascript-typescript-object-null-check
JavaScript/ Typescript object null check?
June 18, 2024 - A variable is undefined until and ... variable null, we must assign it a null value. To check a variable is null or not in typescript we can use typeof or "===" operator....
Honlsoft
honlsoft.com › blog › 2021-07-20-typescript-tips-null-coalescing
Typescript Tips: null(and undefined) Checking | Honlsoft
July 20, 2021 - Thankfully, in Typescript, there are several shorthand ways to deal with nulls. The Elvis operator is a shorthand way to check for null or undefined without requiring a separate if statement.
MDN Web Docs
developer.mozilla.org › en-US › docs › Web › JavaScript › Reference › Operators › Nullish_coalescing
Nullish coalescing operator (??) - JavaScript | MDN
August 26, 2025 - The nullish coalescing (??) operator is a logical operator that returns its right-hand side operand when its left-hand side operand is null or undefined, and otherwise returns its left-hand side operand.
Built In
builtin.com › software-engineering-perspectives › javascript-null-check
How to Check for Null in JavaScript | Built In
Summary: JavaScript offers several ways to check for null, including strict (===) and loose (==) equality, Object.is() and boolean coercion. Developers often use typeof and optional chaining (?.) to safely identify null, undefined or undeclared ...
Published August 4, 2025
Upmostly
upmostly.com › home › typescript › how to detect null and undefined
How to Detect Null and Undefined in Your TypeScript Code - Upmostly
March 28, 2023 - Another way to check for null or undefined is to use the nullish coalescing operator (??), which was introduced in TypeScript 3.7.
GitBook
basarat.gitbook.io › typescript › recap › null-undefined
Null vs. Undefined | TypeScript Deep Dive
August 18, 2020 - Recommend == null to check for both undefined or null.
C# Corner
c-sharpcorner.com › article › explain-null-handling-in-typescript
Explain Null Handling in TypeScript
March 21, 2024 - Null handling in TypeScript involves managing null and undefined values effectively to prevent runtime errors. Techniques like nullable types, optional chaining, type guards, and non-null assertion operators help ensure code reliability.
TypeScript
typescriptlang.org › docs › handbook › 2 › narrowing.html
TypeScript: Documentation - Narrowing
In the printAll function, we try to check if strs is an object to see if it’s an array type (now might be a good time to reinforce that arrays are object types in JavaScript). But it turns out that in JavaScript, typeof null is actually "object"! This is one of those unfortunate accidents of history. Users with enough experience might not be surprised, but not everyone has run into this in JavaScript; luckily, TypeScript lets us know that strs was only narrowed down to string[] | null instead of just string[].
React
react.dev › learn › typescript
Using TypeScript – React
This causes the issue that you need to eliminate the | null in the type for context consumers. Our recommendation is to have the Hook do a runtime check for it’s existence and throw an error when not present: