@[email protected] to Programmer [email protected] • 11 months ago===programming.devimagemessage-square60fedilinkarrow-up1662arrow-down115
arrow-up1647arrow-down1image===programming.dev@[email protected] to Programmer [email protected] • 11 months agomessage-square60fedilink
minus-square@[email protected]linkfedilink2•11 months agoI 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.
minus-square@SzethFriendOfNimilink0•11 months agoTry changing to const === variable. That’s most likely what’s it doing to minimize the risk of accidental assignment.
minus-square@[email protected]linkfedilink3•11 months agoWut? This is an automated optimizer. It is not worried about accidental assignment.
minus-square@SzethFriendOfNimilink1•11 months agoI agree it shouldn’t. But I’ve seen linters that automatically change it since they seem to be forcing practical conventions sometimes.
minus-square@[email protected]linkfedilink3•11 months agoLinters and minifers are completely different tools.
minus-square@SzethFriendOfNimilink3•11 months agoGood point. That’s what I get for shooting from the hip. Thanks!
I just tested and Terser will convert
v === null || v === undefinedtonull==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.Try changing to const === variable. That’s most likely what’s it doing to minimize the risk of accidental assignment.
Wut? This is an automated optimizer. It is not worried about accidental assignment.
I agree it shouldn’t. But I’ve seen linters that automatically change it since they seem to be forcing practical conventions sometimes.
Linters and minifers are completely different tools.
Good point. That’s what I get for shooting from the hip.
Thanks!