-
-
Notifications
You must be signed in to change notification settings - Fork 761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[8.0.0-beta.4] fallbackLng is ignored #953
Comments
I cannot reproduce. If I checkout the module.exports = {
fallbackLng: 'en'
} It works as expected. Please provide repro steps. Thanks! |
I am having the same problem. In serverSideTranslations, only the store for initialLocale is populated and not for the fallback language.
|
I'll need someone to provide a reproducible repository. |
I've been struggling with this since migrating over to the beta branch a few weeks ago (#869 (comment)). I have tried a few times to identify why, and fix it myself, but without any success. I put together this minimum reproduction real quick that is also failing to load fallbackLngs. Hope it helps! https://github.com/dmeents/fallback-ignored-example |
Thanks for the repro, @dmeents. This is indeed a genuine bug, and I will fix it immediately. |
A couple things to note:
|
Describe the bug
dev
is still used as a fallbackLng (missing string for a locale) even when settingfallbackLng: 'en'
Occurs in next-i18next version
8.0.0-beta.4
Steps to reproduce
Setting
fallbackLng: 'en'
innext-i18next.config.js
.Expected behaviour
Should use
en
as fallback language when a string is missing for a locale.The text was updated successfully, but these errors were encountered: