fix: strict equals instead of abstract equals

[gasp]

(minor)

It is considered good practice to use the type-safe equality operators === and !== instead of their regular counterparts == and !=.

The reason for this is that == and != do type coercion which follows the rather obscure Abstract Equality Comparison Algorithm. For instance, the following statements are all considered true:

• [] == false
• [] == ![]
• 3 == "03"

(source)

[SilverD3]

Thanks @gasp . When we run eslint, we can see almost a hundred of this warning (Expected '===' and instead saw '==')

[mwithi]

Reviewed and approved by @SilverD3