vietnamesedeveloper

Yes, but only if your goal is exactly 2 decimal places . Your function: formatNumberWithDecimal(12.345) returns: "12.345" while: (12.345).toFixed(2) returns: "12.35" because toFixed(2) rounds and always produces exactly 2 decimal digits. If you want exactly 2 decimals You can replace the whole function with: export function formatNumberWithDecimal(num: number): string { return num.toFixed(2); } Examples: formatNumberWithDecimal(12); // "12.00" formatNumberWithDecimal(12.5); // "12.50" formatNumberWithDecimal(12.34); // "12.34" formatNumberWithDecimal(12.345); // "12.35" If you want at least 2 decimals but preserve extra precision Then toFixed(2) is not a replacement. Examples: Input Current Function toFixed(2) 12 12.00 12.00 12.5 12.50 12.50 12.34 12.34 12.34 12.345 12.345 12.35 So whether toFixed(2) can replace it depends on the intended behavior. Most applications that display prices, currency, percentages,...

Ecommerce with JS

June 07, 2026

Not quite. It works for many numbers, but there are some edge cases. Your function: export function round2(value: number | string) { if (typeof value === 'number') { return Math.round((value + Number.EPSILON) * 100) / 100; } else if (typeof value === 'string') { return Math.round((Number(value) + Number.EPSILON) * 100) / 100; } else { throw new Error('Value is not a number or string'); } } What it does well round2(1.234); // 1.23 round2(1.235); // 1.24 round2("12.345"); // 12.35 The Number.EPSILON trick helps with some floating-point issues: Math.round(1.005 * 100) / 100 // 1 round2(1.005) // 1.01 What it doesn't guarantee Invalid strings round2("abc") // NaN No error is thrown because "abc" is still a string. You may want: const num = Number(value); if (Number.isNaN(num)) { throw new Error("Invalid number"); } Very large numbers Floating-point precision limits still apply: round2(12345...