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
Variables rendered instead of actual strings (occurs randomly) #1137
Comments
I am also experiencing these problems but with the app router. It has to be something with race condition. BTW in i18n.js file I'am using "loadLocaleFrom" property with "import" |
Any update on this? |
Having the same issue on the production deployment, app is fine in development but it just shows the strings once deployed |
Has anyone found a root cause/fix for this? |
@aralroca are we able to bump this issue? Any idea what might be causing it? |
Please share a repo reproducing the error, otherwise it is very difficult to know what is happening. |
What version of this package are you using?
2.5.3
What operating system, Node.js, and npm version?
Ubuntu 22.04.3 LTS, Node 18.13.0, npm 8.19.3
What happened?
In production, we see variables rendered instead of strings like this:
This started happening after we upgraded to Nextjs 13 and subsequently next-translate 2.5.3 with next-translate-plugin 2.5.3
This only happens when navigating on the client side, i.e. we click a link on a page that has all the strings rendered correctly, and the destination page loads but with string variables. The most annoying part is that it happens randomly. And usually happens after a deployment. It obviously goes away if we refresh the page, which suggests that there's a client-side issue.
We also use
@ducanh2912/next-pwa
however, I'm facing difficulties narrowing it down further.What did you expect to happen?
Strings rendered correctly
Are you willing to submit a pull request to fix this bug?
Yes, if we can identify where the bug is.
The text was updated successfully, but these errors were encountered: