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
Hi,
I'm trying to use the gatsby-theme-i18n-react-i18next theme but facing some hydratation issues.
To reproduce the behavior, you can simply clone this repo and launch the available react-i18next sample in dev:
cd themes-master/starters/example-react-i18next
yarn && gatsby develop
When you click a link for the first time after page load, you can see this error displayed in console: Warning: Cannot update a component (Layout) while rendering a different component (PageRenderer).
Looking at the stacktrace, it seems related to the 'useTranslation' hook of the react-i18next library.
I found this similar issue on the repo of the library : i18next/react-i18next#1124 but this is not very helping (I played with the useSuspense parameter, but it changes nothing apparently).
My question is: what are consequences of this warning ? Is it ok to "live with it" ? Is there some known workarounds?
Thanks !
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to use the
gatsby-theme-i18n-react-i18next
theme but facing some hydratation issues.To reproduce the behavior, you can simply clone this repo and launch the available react-i18next sample in dev:
When you click a link for the first time after page load, you can see this error displayed in console:
Warning: Cannot update a component (
Layout) while rendering a different component (
PageRenderer).
Looking at the stacktrace, it seems related to the 'useTranslation' hook of the react-i18next library.
I found this similar issue on the repo of the library : i18next/react-i18next#1124 but this is not very helping (I played with the useSuspense parameter, but it changes nothing apparently).
My question is: what are consequences of this warning ? Is it ok to "live with it" ? Is there some known workarounds?
Thanks !
The text was updated successfully, but these errors were encountered: