Sourced from react-i18next's changelog.
17.0.13
- fix(types): the selector-form
keyPrefixoverload ofuseTranslation()is now available underenableSelector: 'strict'.useTranslationwas gated ontrue | 'optimize'only, so under'strict'it resolved to the legacy signature and the selector overload disappeared entirely (keyPrefix: ($) => $.ns.foofailed withType '($: any) => any' is not assignable to type 'undefined').Transalready handled all three modes. Companion to the same fix forgetFixedTin i18next#2446. Thanks@​hovelopin(#1930).
addf646
17.0.137c634ee
changelog v17.0.135ceefb0
fix(types): allow selector keyPrefix in useTranslation under
enableSelector '...aa7ba52
chore(examples): require activesupport >= 7.2.3.1 in the RN
Gemfilesec0bb4e
chore(examples): drop react_native_windows and the RN Gemfile.locksaa5fc43
build