Run results for: Number.toLocaleString vs Intl.NumberFormat vs Regex

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36

Browser: Chrome 129

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: one year ago

Regex

30.5M/s

Number.toLocaleString

63K/s

Intl.NumberFormat

61K/s

View exact numbers

Tests:

Intl.NumberFormat
const currencyPlayNumber = 1; const translatedString = new Intl.NumberFormat(undefined, { style: 'currency', currency: 'RUB', }).format(currencyPlayNumber);
Number.toLocaleString
const currencyPlayNumber = 1; const translatedString = currencyPlayNumber.toLocaleString(undefined, { style: 'currency', currency: 'RUB', })
Regex
const currencyPlayNumber = 1; const translatedString = `${currencyPlayNumber}`.replace(/\B(?=(\d{3})+(?!\d))/g, ',');