Confusing behaviour with basic type boolean in TypeScript

Question

From TypeScript webpage: \"The most basic datatype is the simple true/false value, which JavaScript and TypeScript call a boolean value.\"

Ok so far so good, it\'s just

Answer 1

you do not need to compare true/false values with ==/=== because they are already boolean values themselves. thus making it redundant.

so just do if (a) or if (!a)

typescript just wants to optimize your code this way. in vanilla JS it is perfectly fine to do if (a === true)