wrong output with "dot" thousands separator and no decimal part

[usmonster]

It looks like v1.1.8 (#2) introduced a bug:

Example:

> parsePrice('1.234.123 €')
1.234 // 💸

v1.1.6 got this right (1234123).

[usmonster]

Please note that #2/#1 also makes prices like parsePrice('1.234 €') ambiguous.

I'd argue that 1234 would be the reasonable default in such ambiguous cases.

Generally, to avoid ambiguity, I'd recommend reverting the backwards-incompatible change introduced in v1.1.8 (should've probably been v2.0.0) and letting someone make their own fork if they need to support more than 2-digit decimal precision.