Releases: eemeli/intl-pluralrules
v2.0.1
v2.0.0
This release adds support for Intl.PluralRules.prototype.selectRange()
.
The code is now tested against the relevant test262
tests, and its behaviour is more aligned with the documented API. Browser tests are now run by the CI to ensure that the polyfill works in supported browsers (i.e. matching the Browserslist expression > 0.25%, not dead
)
Breaking Changes
- The function exported from
'intl-pluralrules/factory'
gets a new required fourth argument,getRangeSelector
. - The
'intl-pluralrules/pseudo-number-format'
endpoint is dropped (#30) - IE 11 support is dropped (#36)
New Features
- Add support for
selectRange()
(#23)
Other Changes
- Add tests & fixes for test262 compliance (#27)
- Behave more normally for locale resolution (#28)
- Switch from Jest to Mocha, add browser tests (#29)
Full Changelog: v1.3.1...v2.0.0
v2.0.0-1
The main feature of this release is to add & satisfy test262
tests, and to also otherwise make the behaviour more in line with the documented API. Browser tests are now run by the CI to ensure that the polyfill works in IE11.
Released under the next
tag on npm, so install with:
npm install --save-exact intl-pluralrules@next
Breaking Changes
- The
intl-pluralrules/pseudo-number-format
endpoint is dropped #30
Other Changes
- Add tests & fixes for test262 compliance #27
- Behave more normally for locale resolution #28
- Switch from Jest to Mocha, add IE11 browser tests #29
Full Changelog: v2.0.0-0...v2.0.0-1
v2.0.0-0
This release adds support for selectRange()
from Intl.Numberformat v3 (#23), which is currently a Stage 3 proposal. Hence also the prerelease versioning, as that API may still change.
Released under the next
tag on npm, so install with:
npm install --save-exact intl-pluralrules@next
Breaking Changes
- The function exported from
'intl-pluralrules/factory'
gets a new required fourth argument,getRangeSelector
.