One neat feature is you can compare to both null and undefined at the same time, without other falsey values giving false positives. Although that's not necessary as often now that we have nullish coalescing and optional chaining.

[–] kevincox@lemmy.ml 2 points 9 months ago (1 children)

I just tested and Terser will convert v === null || v === undefined to null==v. Personally I would prefer to read the code that explicitly shows that it is checking for both and let my minifier/optimizer worry about generating compact code.

[–] SzethFriendOfNimi@lemmy.world 0 points 9 months ago (1 children)

Try changing to const === variable. That’s most likely what’s it doing to minimize the risk of accidental assignment.

[–] kevincox@lemmy.ml 3 points 9 months ago (1 children)

Wut? This is an automated optimizer. It is not worried about accidental assignment.

[–] SzethFriendOfNimi@lemmy.world 1 points 9 months ago (1 children)

I agree it shouldn’t. But I’ve seen linters that automatically change it since they seem to be forcing practical conventions sometimes.

[–] kevincox@lemmy.ml 3 points 9 months ago (1 children)

Linters and minifers are completely different tools.

[–] SzethFriendOfNimi@lemmy.world 3 points 9 months ago

Good point. That’s what I get for shooting from the hip.

Thanks!