![JavaScript Type Coercion (Implicit Conversion) and Why to use “===” and avoid “==”. | by Parag Patil | ITNEXT JavaScript Type Coercion (Implicit Conversion) and Why to use “===” and avoid “==”. | by Parag Patil | ITNEXT](https://miro.medium.com/max/521/1*Ss229jCD7x4PBtGib8Sbqw.png)
JavaScript Type Coercion (Implicit Conversion) and Why to use “===” and avoid “==”. | by Parag Patil | ITNEXT
![Minko Gechev on Twitter: "✨ TypeScript protip: don't use the types String, Number, and Boolean. They refer to reference types. It's easy to shoot yourself in the foot when applying equality, although Minko Gechev on Twitter: "✨ TypeScript protip: don't use the types String, Number, and Boolean. They refer to reference types. It's easy to shoot yourself in the foot when applying equality, although](https://pbs.twimg.com/media/EO8vTv9WAAAV3B3.jpg)
Minko Gechev on Twitter: "✨ TypeScript protip: don't use the types String, Number, and Boolean. They refer to reference types. It's easy to shoot yourself in the foot when applying equality, although
Type narrowing in loose equality fails for edge cases like empty string and zero · Issue #37251 · microsoft/TypeScript · GitHub
![bigint' is not comparable to 'number' with loose equality · Issue #30540 · microsoft/TypeScript · GitHub bigint' is not comparable to 'number' with loose equality · Issue #30540 · microsoft/TypeScript · GitHub](https://user-images.githubusercontent.com/13982338/54812603-7152d400-4cc6-11e9-95d3-483025789a7c.png)