To be fair in a dynamic typed language with dumb string to int coercions, I kinda get why such a library would exists. So it's more a symptom of terrible language design than modern dependency hell.

[–] bobo@lemmy.ml 7 points 8 hours ago* (last edited 8 hours ago) (1 children)

in a dynamic typed language with dumb string to int coercions, I kinda get why such a would library exists.

If string return nan, else % 2

So it's more a symptom of terrible language design than modern dependency hell.

Dependency chain: is-even depends on is-odd which depends on is-number

[–] Decq@lemmy.world 1 points 7 hours ago* (last edited 7 hours ago) (2 children)

If string return nan, else % 2

So now you return a number type if it's a string and a boolean if it's an integer. How does that make sense?

The is-even lib exists to sanitize input by throwing an exception which imho is better.

Edit: having looked at the code better. Apparently it still allows string coercion (boo). It only checks for non integer numbers.

[–] bobo@lemmy.ml 1 points 6 hours ago

Good point, but you can do if === true... and else if === false...

But definitely better to throw an error instead of nan.