🌍 A toolbox for your React Native app localization
AndroidManifest.xml
namespace deprecation warningRNLocalizeSpec.h
import when new architecture is enabled (fix #238)LocaleListCompat.getDefault()
to fix preferred languages list order in some rare cases (fix #236)namespace
conditionally in order to improve old react native version compatibility.
⚠️ Note that this library officially now follows the React Native releases support policy. If you have been impacted by this bug, that means you are using an unsupported react native version and should upgrade to the latest.
namespace
for react native 0.73 compatibilityThis release come with a huge change underneath: Instead of constants, the library now perform synchronous methods calls (on both old and new architecture), which means the returned informations will always be up-to-date (fixes https://github.com/zoontek/react-native-localize/issues/186).
This also means that remote debugging (e.g. with Chrome) is no longer possible and that you should switch to Flipper 🐬 (an acceptable trade-off as remote debugging isn't possible with the new architecture anyway)
react-native-windows
(temporarily)react-native
, react-native-macos
< 0.70react-native-web
< 0.18addEventListener
as you can now safely rely on AppState
and get the possible new value when app become active
(fixes https://github.com/zoontek/react-native-localize/issues/91)getCalendar
can now return all supported macOS calendars (buddhist
, coptic
, ethiopic
, hebrew
…)findBestAvailableLanguage
has been renamed findBestLanguageTag
import * as Localize from "react-native-localize"
insteadusesAutoDateAndTime
and usesAutoTimeZone
mocks (#213 by @ethanneff)@formatjs/intl
instead of i18n-js