Adriano Raiano
Adriano Raiano
> @adrai din try v15.0.3 but i managed to get past the error using `v15.0.2` @anniewey can you describe how you solved it?
Please create a minimal reproducible github repository that shows your issue. //cc @marcalexiei
as long as there is V3 support that does not use the Intl api => https://github.com/i18next/i18next/blob/master/src/PluralResolver.js#L99 we can't merge this... but we can consider this like (https://github.com/i18next/i18next/pull/2184) for the next...
Just released v23.16.0 that will use `Intl.getCanonicalLocale` if available...
regarding the lowerCaseLng... this was a user request long time ago... and part of i18next since v1.2.3... isn't it @jamuhl ?
> Just as a FYI, it would be really nice if you used PRs so other people like myself can watch for new PRs. Commits to master does not have...
> It should not be up to you as a maintainer to support 10 year old browsers. i18next is not only used in browsers... but also react-native, hexo, server side,...
btw: [most users will just downgrade](https://github.com/i18next/react-i18next/issues/1797) to still continue to work with i18next... and if they find some bugs or missing functionality etc... we are then forced to address that...
> Newer applications and users should not have to suffer from bloated code or performance hits just because unsupported environments don't support a built in object or newer syntax. If...
Have you tried with this? https://www.i18next.com/principles/fallback#calling-with-fallback-keys