<blockquote>
The equality operator (==) checks whether its two operands are equal, returning a Boolean result.
</blockquote>
If one of the operands is a boolean, it'll convert the boolean operand to 1 if it is <code>true</code> and +0 if it is <code>false</code>. Other operands are also converted to Number and then compared.
Remember,
<pre class="shiki github-dark shaku"><code>Number(false) // 0Number("") // 0Number([]) // 0Number(undefined) // NaNNumber(null) // 0Number(true) // 1Number('1') // 1Number(1n) // 1Number(' 1 ') // 1</code></pre>
Applying this knowledge here—
<pre class="shiki github-dark shaku"><code>console.log(0 == false) // 0 == 0 -&gt; trueconsole.log('' == false) // 0 == 0 -&gt; trueconsole.log([] == false) // 0 == 0 -&gt; trueconsole.log(undefined == false) // NaN == 0 -&gt; falseconsole.log(null == false) // 0 == 0 -&gt; false 🤯console.log('1' == true) // 1 == 1 -&gt; trueconsole.log(1n == true) // 1 == 1 -&gt; trueconsole.log(' 1 ' == true) // 1 == 1 -&gt; true</code></pre>
As you can see, <code>null</code> is an exception to this rule. The details are slightly more technical and this is just a behavior of how <a href="http://es5.github.io/#x11.9.3">The Abstract Equality Comparison Algorithm</a> works. However, just remember in a simple way the conversion of null to number is not done automatically, hence <code>null</code> is not equal to either <code>true</code> or <code>false</code>.
In fact, if you do it explicitly you'll see that it works properly,
<pre class="shiki github-dark shaku"><code>null == false // falsenull == true // false// But if we do the coercion explicitly it works+null == false // true+null == true // false</code></pre>
If interested go through this very helpful SO thread <a href="https://stackoverflow.com/questions/27632391/why-null-false-and-null-true-both-return-false">https://stackoverflow.com/questions/27632391/why-null-false-and-null-true-both-return-false</a>

Weird case of null == false

What does the code snippet to the right output by console.log?…