You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest with-react-intl example #16215 has a few issues:
The extracted message ids don't match the ones produced in the .next cache. The compiled langs are therefore not used and default to the ones defined in the components.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 29, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
The latest
with-react-intl
example #16215 has a few issues:.next
cache. The compiled langs are therefore not used and default to the ones defined in the components.The translation happens only client side.
When navigating to a different page the locale is undefined and defaults back to
en
.To Reproduce
with-react-intl
exampleyarn build && yarn start
.next
cache to match those incompiled-lang
Expected behavior
Screenshots
System information
The text was updated successfully, but these errors were encountered: