Reinier Kaper
Hydration error with i18n
Okay this still keeps happening, I have a feeling it's based on the user's OS.
Previously this was an issue too, where the following oddity occurred:
- English OS - English i18n selection: good
- English OS - French i18n selection: good
- French OS - English i18n selection: good
- French OS - French i18n selection: server render in English
I wonder if this is still an issue, as I see people landing on
/fr/some-route
and the server rendering in English again.
I will investigate more today, hopefully I can reproduce it again like last time. At least I now know where to look.
Additional question: if people visited the site before (say a week ago) and they revisit again today (fixed version of the site), would there still be something cached (cookie/localstorage/broswer-cache/etc?) that could cause the "old" behaviour temporarily?27 replies
Hydration error with i18n
Interesting: after releasing our update in the wild, we now seem to get to opposite issue: where the server renders French, instead of English (the requested language).
I'll keep an eye on it, but this feels like the fix wasn't fully effective
27 replies
Hydration error with i18n
Yeah I'm trying to get the starter to fail, but I can't.
It's something in our project, but even if I disable all other modules it seems to go wrong.
Very hard to pin-point and we can't update Nuxt because it brakes other modules.
I'll see if I can update to latest i18n though and see if that helps
27 replies
Hydration error with i18n
@Bobbie sorry for the ping.
I can't repro this in Stackblitz, everything looks normal there. Our config is pretty much the same, but for some reason the server always returns
en
, instead of the right locale.
Any pointers as to where we might need to look?
This is our config:
And root config file
27 replies
Is there a way generating openapi client for Nuxt fetch API
Would this work? https://github.com/enkot/nuxt-open-fetch
We use it to generate our own clients with
5 replies