When should I use ?? (nullish coalescing) vs || (logical OR)?

Question

Related to Is there a "null coalescing" operator in JavaScript? - JavaScript now has a ?? operator which I see in use more frequently. Previously most JavaScript code used ||.

let userAge = null

// These values will be the same. 
let age1 = userAge || 21
let age2 = userAge ?? 21

In what circumstances will ?? and || behave differently?

Rightist

Overview and motivation – Monroe

Answer 1

The OR operator || uses the right value if left is falsy, while the nullish coalescing operator ?? uses the right value if left is null or undefined.

These operators are often used to provide a default value if the first one is missing.

But the OR operator || can be problematic if your left value might contain "" or 0 or false (because these are falsy values):

console.log(12 || "not found") // 12
console.log(0  || "not found") // "not found"

console.log("jane" || "not found") // "jane"
console.log(""     || "not found") // "not found"

console.log(true  || "not found") // true
console.log(false || "not found") // "not found"

console.log(undefined || "not found") // "not found"
console.log(null      || "not found") // "not found"

In many cases, you might only want the right value if left is null or undefined. That's what the nullish coalescing operator ?? is for:

console.log(12 ?? "not found") // 12
console.log(0  ?? "not found") // 0

console.log("jane" ?? "not found") // "jane"
console.log(""     ?? "not found") // ""

console.log(true  ?? "not found") // true
console.log(false ?? "not found") // false

console.log(undefined ?? "not found") // "not found"
console.log(null      ?? "not found") // "not found"

While the ?? operator isn't available in current LTS versions of Node (v10 and v12), you can use it with some versions of TypeScript or Node:

The ?? operator was added to TypeScript 3.7 back in November 2019.

And more recently, the ?? operator was included in ES2020, which is supported by Node 14 (released in April 2020).

When the nullish coalescing operator ?? is supported, I typically use it instead of the OR operator || (unless there's a good reason not to).

Emanate

Answer 2

In short

The Nullish Coalescing Operator ?? distinguishes between:

• nullish values (null, undefined)
• falsey but defined values (false, 0, '' etc.)

|| (logical OR) treats both of these the same.

I created a simple graphic to illustrate the relationship of nullish and falsey values in JavaScript:

Further explanation:

let x, y

x = 0
y = x || 'default'            // y = 'default'
y = x ?? 'default'            // y = 0

As seen above, the difference between the operators ?? and || is that one is checking for nullish values and one is checking for falsey values. However, there are many instances where they behave the same. That is because in JavaScript every nullish value is also falsey (but not every falsey value is nullish).

Using what we learned above we can create a few examples for different behavior:

let y

y = false || 'default'       // y = 'default'
y = false ?? 'default'       // y = false

y = 0n || 'default'          // y = 'default'
y = 0n ?? 'default'          // y = 0n

y = NaN || 'default'         // y = 'default'
y = NaN ?? 'default'         // y = NaN

y = '' || 'default'          // y = 'default'
y = '' ?? 'default'          // y = ''

Since the new Nullish Coalescing Operator can differentiate between no value and a falsey value, it can be beneficial if you, for example, need to check if there is no string or an empty string. Generally, you probably want to use ?? instead of || most of the time.

Last and also least here are the two instances where they behave the same:

let y

y = null || 'default'        // y = 'default'
y = null ?? 'default'        // y = 'default'

y = undefined || 'default'   // y = 'default'
y = undefined ?? 'default'   // y = 'default'

Masquerade

The graphic alone gives an awesome explanation at a glance - nice one! – Compendious

Love that explanation. On Point! – Dagostino

remembers me of an ancent wat video. some more falsey examples: 0.0, 0x0, 0b0, 0e0, -0e123 0e-123, and of course combinations: -1.2e-1234 – Systematist

Answer 3

As a very short rule, you could look at it the opposite way:

• || (or) returns the first "truthy" value (or the last value if no "truthy" value exists)
• ?? (nullish coalescing) returns the first "defined" value (or the last value if no "defined" value exists)

Example

x = false || true; // -->  true   (the first 'truthy' value - parameter 2)
x = false ?? true; // -->  false  (the first 'defined' value - parameter 1)

Oversubscribe

Answer 4

As described in the MDN:

Contrary to the logical OR (||) operator, the left operand is returned if it is a falsy value which is not null or undefined. In other words, if you use || to provide some default value to another variable foo, you may encounter unexpected behaviors if you consider some falsy values as usable (eg. '' or 0). See below for more examples.

And also in the answer to the question you linked:

Regardless of the type of the first operand, if casting it to a Boolean results in false, the assignment will use the second operand. Beware of all the cases below:

alert(Boolean(null)); // false
alert(Boolean(undefined)); // false
alert(Boolean(0)); // false
alert(Boolean("")); // false
alert(Boolean("false")); // true -- gotcha! :)

Grandmotherly

I did see that description in that questions answer, but it's seemed like a repeat of well known JS boolean logic rather than a specific example. – Rightist

Answer 5

Base on MDN docs:

Contrary to the logical OR (||) operator, the left operand is returned if it is a falsy value which is not null or undefined.

Conceptual Example:

• When use || for a falsy value that is NOT undefined or null:

  false || 'name'; // ==> the 'name' is returned
  

• But when using ?? for above case:

  false ?? 'name'; // ==> the false is returned
  
  

Real Example: Assume, we have a phone variable that is not mandatory in our form and the empty string ('') is valid for us and we wanna doSomething() if the phone variable is null or undefined, now guess what:

• When use || for a falsy value that is NOT undefined or null:

  const phone = ''; // assume it became empty string from some action
  
  phone || doSomething(); // ==> damn, the doSomething is run 
  // but we want to run it if it's `undefined` or `null` the empty string is valid for us
  

• But when using ?? for above case:

  const phone = ''; // same assumption like above
  
  phone ?? doSomething(); // ==> yeah, that's right
  // the empty string is valid for us and the doSomething is not run
  

Note: actually it is an example and in a real project you can have a better sense of this lovely operation usage.

Attention: for the undefined or null both of them act like each other.

Rockhampton

Answer 6

When the || is being used as a boolean conditional that goes to false. For example:

let userAge = false

// These values will be the same. 
let age1 = userAge || 21 // 21
let age2 = userAge ?? 21 // false

The logical OR will still give the next value for anything that doesn't evaluate to true. So it gives the value 21 in this case. Where ?? only handles null and undefined.

Carlyncarlynn

Answer 7

function f(input) {
  const val = input || 1;

  return 41 + val;
}

function g(input) {
  const val = input ?? 1;

  return 41 + val;
}

console.log("using ||:", f(0));
console.log("using ??:", g(0));

The null(ish) coalescing operator only works with null and undefined. So, use the null(ish) coalescing operator when you don't want those values but you will otherwise accept other falsy values:

console.log(null      ?? "nullish");
console.log(undefined ?? "nullish");
console.log(""        ?? "nullish");
console.log(0         ?? "nullish");
console.log(false     ?? "nullish");

The logical OR will skip over any falsy value and give you the other thing. The logical OR will skip over any falsy value and give you the other parameter. This does work and is by now idiomatic, however it is not always what you want:

console.log(null      || "falsy");
console.log(undefined || "falsy");
console.log(""        || "falsy");
console.log(0         || "falsy");
console.log(false     || "falsy");

Here are few rules for how to determine which one you need. The simplest tests:

• do you only want to protect against null (and undefined - it's usually the same thing)? Then use ??. If you aren't sure, it's probably a good idea to default to the nullish coalescing operator.
• do you know you also don't want 0 or "", for example? Then use ||.

The second one is where it actually gets trickly. How do you know you need to discard falsy values? Well, the very first snippet shows what happens if you do that: f(0) will discard the zero and thus produce a different result. This is a somewhat common source of bugs. Since the construct a = b || c is common to introduce a fallback value (in this case c) it might accidentally fall back to it when you didn't mean to.

function updateAge(years) {
  var yearsToAdd = years || 1;
  return this.age + yearsToAdd
}

This works if you want to provide a fallback for calling updateAge() (no argument) but fails if you call updateAge(0) (no update). Similarly, you could have:

function sayMyName(greeting) {
  var prefix = greeting || "Hello, my name is ";
  return prefix + this.firstName;
}

Again, this works for sayMyName() (no argument) but fails for sayMyName("") (explicitly no greeting).

To generalise, if you are providing a fallback value that's different to the falsy value, then you might have a problem. However, if your fallback is the falsy value - num || 0 or str || "" then it doesn't really matter.

It's rare (or should be) that you might expect a mixed type (number, or string, or object, etc) and provide a fallback to it: input || fallback is valid but will reject empty strings and zeroes. It's usually going to be wrong unless you explicitly don't want any of those.

To put it simply, you should likely use the nullish coalescing operator ?? at all times. It will be less cognitive load to figure out whether it's a potential bug or not. There is also not much reason to avoid it. It's newer than the boolean OR, so it doesn't work on older environments, that's true, however nowadays you should likely be transpiling your code for those. If you cannot or prefer not to, then you don't have a choice and should use the boolean OR.

Rimskykorsakov

Thanks @vlaz, that's the clearest answer (I boldest the best part) - both the how to judge when to use ?? or ||, and some examples. – Rightist

@Rightist I'm working on those :D Short answer - if you want to protect against null then use ??. If you want to discard zero and empty string, then use ||. Honestly, I can't think of many reasons you'd want || nowadays except if you support older environments and don't transpile your code. But that's sort of niche anyway. – Rimskykorsakov

Answer 8

In short, when you care that let a variable assigned from a possible null undefined source, and you wish to provide a default value to the variable, use the nullish coalescing operator ??.

If you want to avoid messing yourself around with the JavaScript definition of falsy truthy [1], then avoid using ||.

nullish coalescing operator ??

JavaScript definition of falsy

a real example in angular

/* parse the url pattern 
/search?keyword=mykeyword&page=3
/search?keyword=mykeyword
*/

  ngOnInit(): void {
    const keyword = this.route.snapshot.queryParamMap.get('keyword') ?? 'default keyword';
    const page = this.route.snapshot.queryParamMap.get('page') ?? '0';
    this.queryResult$ = this.service.getQueryResult(keyword, +page);
    this.keyword = keyword;
  }

[1]: Each programming language has its own definition of falsy truthy. The basic approach to tell whether a value is a truthy value is that if the explicit type conversion function bool(value) results in true, then the value is truthy.

For those might work across languages, PHP and C# also have ??. See PHP, C#.

Tolman

As some feedback, this doesn't read very well: "if you want to avoid X, don't do Y". Thanks for taking the time to answer though. – Rightist