Number Formatter

In-Depth Guide

Locale-aware number formatting — inserting thousands separators, selecting the decimal mark, positioning the currency symbol, and choosing minimum and maximum fraction digits — is one of the most underestimated pieces of localisation work in front-end development. The same number, 1234567.89, is rendered '1,234,567.89' in en-US, '1.234.567,89' in de-DE, '1 234 567,89' in fr-FR (with a non-breaking thin space as the thousands separator per CLDR), and '12,34,567.89' in en-IN (Indian grouping by lakhs and crores). FastTool's number formatter wraps the browser's Intl.NumberFormat API (ECMAScript Internationalisation API, ECMA-402) and exposes every option the spec supports: style (decimal, currency, percent, unit), currency code (ISO 4217), notation (standard, scientific, engineering, compact), and locale (BCP 47 tag). The answer always matches what the user's operating system would produce in the same locale, so there is no drift between tool output and production rendering.

Why This Matters

Mis-formatting a number in a localised user interface is both a correctness bug and a trust issue. A German user seeing '1,234.56' reads it as 'one point two three four five six' (a decimal close to one) because the comma is their decimal separator. A financial app that mixes locale conventions can show a user €1,00 when it meant €1.00 × 100 = €100 and lose a customer in the resulting support ticket. A canonical formatter bound to CLDR data keeps the output consistent with every other professional system the user interacts with.

Real-World Case Studies

• Multi-region invoice generation. A SaaS billing engineer testing the invoice renderer runs 1234567.89 through the formatter in four target locales: en-US gives '$1,234,567.89', de-DE gives '1.234.567,89 €', ja-JP gives '¥1,234,568' (zero fraction digits for JPY by ISO 4217 E.1), and en-IN gives '₹12,34,567.89'. She files a bug against her backend because the Japanese invoice was showing two decimal places, which would confuse accountants who never see fractional yen.
• Scientific paper value formatting. A PhD student preparing a manuscript uses the formatter's scientific notation mode on 6.02214076 × 10²³ (the Avogadro constant, fixed by the 2019 SI redefinition). She copies '6.02214076E23' for plain-text submission and '6.022 140 76 × 10²³' (thin-space grouping per NIST SP 811 §10.5) for camera-ready. Both forms come from the same input via different options, which lets her match her journal's style guide without manually typing Unicode superscripts.
• E-commerce product page. A front-end developer building a marketplace prototype uses the formatter in compact-notation mode to render large view counts: 12345 becomes '12K', 1234567 becomes '1.2M', 1234567890 becomes '1.2B'. The compact forms come from CLDR data and automatically localise — '12K' in en-US becomes '12 Tsd.' in de-DE, '1.2万' in ja-JP, and '1,2 K' in fr-FR. He ships the feature without a single hand-written translation string.

Technical Deep Dive

The formatter delegates to Intl.NumberFormat(locale, options), whose behaviour is specified by ECMA-402 and backed by CLDR (Unicode Common Locale Data Repository) via the browser's ICU implementation. Options include style ('decimal', 'currency', 'percent', 'unit'), currency (ISO 4217 three-letter code like USD, EUR, JPY — each with a canonical number of decimal places), minimumFractionDigits and maximumFractionDigits (0 to 20), notation ('standard', 'scientific', 'engineering', 'compact'), useGrouping (true/false/'min2'/'auto'), and locale-sensitive defaults for grouping (Western 3-digit vs Indian 2-2-3 lakhs). Rounding follows the IEEE 754 round-half-to-even rule unless a roundingMode option overrides it. Numbers outside the double-precision range lose low-order digits; for exact arbitrary-precision formatting, pass a BigInt or string input, which the newer ES2023 Intl.NumberFormat accepts directly. Currency formatting respects each currency's default minor-unit count from ISO 4217 Annex E — two decimal places for most, zero for JPY and KRW (where fractional units were retired decades ago), three for KWD and BHD, and four for some precious-metal codes. Unit formatting supports the full MeasureUnit list from CLDR (metre, kilogram, second, celsius, kilometer-per-hour, and over 70 others) with automatic plural form handling.