Closed danielsogl closed 5 years ago
PR welcome
I mentioned the issue also here https://github.com/i18next/i18next-xhr-backend/pull/319#issuecomment-517946389
Thank you for mentioning...but I guess all are aware of the problem ... and mentioning it won't fix it magically...
Myself and others that worked on the types made the mistake of thinking that the signature was use(instance)
, not use(classOrObject)
in the upstream types (which it is).
I'm adding a test here which confirms the breakage and will figure out the upstream type change in #322
If you are not already aware, you can temporarily workaround this issue with .use(XHR as any)
.
Fix is merged to i18next. Once released, everyone should be good. I'm sorry I mixed this up, it was my misunderstanding of the runtime when tightening the types of the arguments.
Tests added here in #322 to make sure local types are conforming in the future.
i18next-xhr-backend@3.1.1 i18next@17.0.9
I updates my i18next des to their latest releases and received following error