Unfortunately I don't think this is good advice. It's technically correct, yes, but being able to constrain the type of some variable is the entire point of TypeScript. Our first suggestion here should be to use that capability, not to improve our runtime type checks.

:) You're welcome!

Thanks! You could still use parseInt and parseFloat, or "+" depending on the use case (i.e. parsing strings with non-numerical characters vs. parsing hex values), but I find "+" convenient for working with TypeScript in general.

Here is a helpful table for reference:
https://i.stack.imgur.com/QNMfI.png

*Lol at second glance it appears I accidentally flipped the params in reduce. Should be:
.reduce((acc, n) => acc + n)