Haven't done any testing around them yet, so no idea what the behaviour is like, but pretty sure my regex will pretty much rule out any possible compatibility with them in UnitValue.parse()

So... need to support negative values consistently throughout the library.

The current regex already doesn't allow for whitespace forming part of either the <number> or <units> segments so this should be trivial.

For the original intended use case, no space makes sense, e.g. working with strings like "50em" or "10px".

However the parse-unit example is "50 gold" and having a space is perfectly reasonable there.

So for added utility we should allow (but not require) whitespace in input strings with units (i.e. in parseString().

Add friendly / readable aliases for the math helpers so calls read more naturally.

Add -> Plus
Subtract -> Minus
Multiply -> Times

nuff said

should have some more for qol / safety. e.g. build before publish