Recently found that formatting method which simplify the management of digits after comma

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#style

new Intl.NumberFormat('de-DE', { style: 'percent', maximumFractionDigits: 2  }).format(
    number,
  ),

I don't think using the number format would be better in this case, we are clipping the number number so they are easier to read, yes, but they also need to be a numeric value, while Intl.NumberFormat would format it to a user to see, like adding . in the hundreds, eg: 1000 -> 1.000

What triggered me is the .toFixed(2) before parsing.

You have do

1. number computation (v * v2) / 100)
2. transformation to string .toFixed(2)
3. transformation to number Number.parseFloat()

Whereas you could

1. have the correct numbers by doing only the (v * v2) / 100) in the normalize
2. display value as expected with

const valueFormatter = new Intl.NumberFormat('de-DE', { style: 'percent', maximumFractionDigits: 2  }).format;

Intl.NumberFormat would format it to a user to see, like adding . in the hundreds, eg: 1000 -> 1.000

Yes, and with style: 'percent' it will add the percentage sygn, plus some space according to the locale, an manage rounding the values to get the correct number of digits, ...

Ah, that could be an options yes.

I don't think it matters much though, since we also have the data as 11.11 in the other dataset, this ensures all datasets have the same precision. 😅