You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting an error (NOBRIDGE) ERROR [Error: FORMATTING_ERROR: Cannot read property 'prototype' of undefined] [Component Stack]
here my full setup
import*asLocalizationfrom"expo-localization";import{Settings}from"luxon";importtype{IntlConfig}from"use-intl";importfrfrom"./locales/fr.json";importenfrom"./locales/en.json";// https://formatjs.github.io/docs/polyfills/intl-pluralrules/import"@formatjs/intl-pluralrules/polyfill-force";import"@formatjs/intl-pluralrules/locale-data/en";import"@formatjs/intl-pluralrules/locale-data/fr";Settings.defaultLocale=Localization.getLocales()[0].languageCode??"en";Settings.defaultZone=Localization.getCalendars()[0].timeZone??"Europe/Paris";constTranslations={
fr,
en,}asconstsatisfiesRecord<string,unknown>;exportconstIntlContextConfig: IntlConfig={locale: Settings.defaultLocale,messages:
Translations[Settings.defaultLocaleaskeyoftypeofTranslations]??Translations.en,};typeMessages=(typeofTranslations)["en"];declare global {// Use type safe message keys with `use-intl`interfaceIntlMessagesextendsMessages{}}
Describe the solution you'd like
I would like a working solution for react native with expo.
Describe alternatives you've considered
Not using plural ? 😅
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In react native you don't have Intl.PluralRules yet.
https://formatjs.github.io/docs/polyfills/intl-pluralrules/#react-native might help, but still after
I'm getting an error
(NOBRIDGE) ERROR [Error: FORMATTING_ERROR: Cannot read property 'prototype' of undefined] [Component Stack]
here my full setup
Describe the solution you'd like
I would like a working solution for react native with expo.
Describe alternatives you've considered
Not using plural ? 😅
The text was updated successfully, but these errors were encountered: