I am using a backend plugin to fetch translations from an external API. I am getting the translations from the API but I am getting a CORS error in the client and the data isn't being set/sent to the client, even though I am able to parse it on the sever.
For the sake of testing, I am only sending 1 namespace, 'common' and only one locale, 'en'. Not sure if this will affect my outcomes.
Occurs in next-i18next version
"next-i18next": "^4.4.2"
Steps to reproduce
i18n.ts
If loading from a backend, do I need localePath set in the config object? or what should it be set to instead?
Inside of the translations condition, I am able to successfully log the returned namespace translations, and send them to the callback as instructed, but on my FE, when I log i18n, and inspect the store, the common bundle is empty.
OS (please complete the following information)
Device: MBP 2019 15"
Browser: Chrome Version 83.0.4103.97 (Official Build) (64-bit)
Describe the bug
I am using a backend plugin to fetch translations from an external API. I am getting the translations from the API but I am getting a CORS error in the client and the data isn't being set/sent to the client, even though I am able to parse it on the sever.
For the sake of testing, I am only sending 1 namespace, 'common' and only one locale, 'en'. Not sure if this will affect my outcomes.
Occurs in next-i18next version
"next-i18next": "^4.4.2"
Steps to reproduce
i18n.ts
localePath
set in the config object? or what should it be set to instead?backend.ts
Expected behaviour
Inside of the
translations
condition, I am able to successfully log the returned namespace translations, and send them to the callback as instructed, but on my FE, when I logi18n
, and inspect the store, the common bundle is empty.OS (please complete the following information)