NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Locale-aware amount formatter with a native bridge that reads the device's true Region setting — the one that drives the numeric keyboard's decimal key.
Last release 3 months ago
10 Jul 2026
Too new to tell
only 1 release windows
Nearly every release is documented
notes for 4 of 4 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
4 releases · first in 2026
One column per month.
v2.0.1 — add 26 missing ISO 3166-1 country codes
v2.0.1 — add 26 missing ISO 3166-1 country codes
Additive
AmountInputLocale._byCountry coverage. No API changes; countries
previously falling back to commaGroupDotDecimal now resolve to their
CLDR-appropriate format:
BQ, CW, SX (Dutch Caribbean, USD in
practice); TK, AS, GU, MP (Oceania US-influenced); AQ, HM
(uninhabited, neutral default).AW (Aruba, nl); GL (Greenland, da/kl).GF, MF, BL, PM, RE, YT, NC,
PF, WF, TF (French overseas); AX (Åland, sv/fi); BV (Bouvet,
Norwegian territory).Removed DeviceRegionService . Init is now a single call on the headline class:
Removed DeviceRegionService. Init is now a single call on the headline class:
// Before (1.x)
await DeviceRegionService.initializeAndApply();
// After (2.0)
await AmountLocalizer.ensureInitialized();Removed the top-level DeviceRegionService export from the public barrel. The platform bridge is now a library-private implementation detail.
Tests can reach the underlying MethodChannel via @visibleForTesting AmountLocalizer.debugChannel.
Replace every DeviceRegionService.initializeAndApply() callsite with AmountLocalizer.ensureInitialized(). Same semantics, same return type (Future<String?>), same best-effort / never-throws contract.
dependencies:
amount_localizer: ^2.0.0📦 pub.dev: https://pub.dev/packages/amount_localizer/versions/2.0.0
First stable release. No API changes vs 0.1.1 — the public surface is now covered by semver, so any breaking change from here on will require a 2.0.0.
First stable release of amount_localizer — a locale-aware amount formatter for Flutter with a native bridge that reads the device's true Region setting.
Flutter's PlatformDispatcher.instance.locale only exposes the language locale. On an English-language iPhone with Region = Brazil, Dart sees en_US, but the numeric keyboard emits , for the decimal. Users in that setup can't type an amount because the display formats with . but the keyboard produces ,. This plugin closes that gap.
AmountInputLocale — canonical enum of numeric formats (1,234.56 / 1.234,56 / 1 234,56 / Indian lakhs / …) with country and Locale resolvers.AmountLocalizer — cached intl-backed formatter with banking defaults and a .localizedAmount extension on Object.DeviceRegionService — one call at app startup that reads the device region over a MethodChannel and applies it to AmountInputLocale.regionOverride.Locale.current.region (iOS 16+) / regionCode (older).Locale.getDefault(Locale.Category.FORMAT).country.First stable release. No API changes vs 0.1.1 — the public surface is now covered by semver, so any breaking change from here on will require a 2.0.0.
dependencies:
amount_localizer: ^1.0.0AmountInputLocale — canonical numeric-format enum with country/locale resolution.
AmountInputLocale — canonical numeric-format enum with country/locale resolution.AmountLocalizer — cached, locale-aware amount formatter.DeviceRegionService — native bridge that reads the device's true Region /
format-locale country and applies it to AmountInputLocale.regionOverride.Your coding agent can read these notes before it upgrades. Set up the MCP server →