i18next-browser-languageDetector | language detector used in browser environment for i18next

The loadPath function is just there to get the path to load, not the actual load request.

To do so use the request option:

https://github.com/i18next/i18next-http-backend#backend-options

Try something like this:

First, this error message is indeed expected on Jan. 11th, 2022.
See "Improving Git protocol security on GitHub".

January 11, 2022 Final brownout.

This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol.
This will help clients discover any lingering use of older keys or old URLs.

Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR.

As noted by Jörg W Mittag:

There was a 4-month warning.
The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it's not like this is a huge surprise.

Personally, I consider it less an "issue" and more "detecting unmaintained dependencies".

Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem.

The permanent shutdown is not until March 15th.

As in actions/checkout issue 14, you can add as a first step:

Well, by debugging a little bit I've managed to solve this JS-Kotlin bridging issue. The working solution is the following declaration:

Try something like this:

By default i18next sets the ns and defaultNS option to 'translation' https://www.i18next.com/overview/configuration-options#languages-namespaces-resources

If you do not have that namespace, set those options to a different value, i.e.:

Since you have a dependency of apiDelegate fn, you need to init the i18next after calling the API. Then only you can able to access the output variable result.

Updated As await at top level is not supported

I would suggest to use another plugin i18next-http-backend as i18next has mentioned here

You need to install the plugin first npm i i18next-http-backend

Then just define the backend. There are some examples here

If you need your consumers to wait until the language has been setup, you could return a promise from this module instead. Something like:

I just found out that i had to make a certain file shareable:

'angular-i18next': { singleton: true, strictVersion: true, requiredVersion: 'auto' },