Aral Roca Gomez

@nbouvrette yes, `DynamicNamespaces` [loads the translations in a `useEffect`](https://github.com/vinissimus/next-translate/blob/master/src/DynamicNamespaces.tsx#L30) so in SSR it will only load the spinner or skeleton. Next-translate is designed to control translations at the page level,...

@nbouvrette I wish I would help you, but I'm struggling to see how we could implement that each component would have its own JSON but at the same time if...

I am with you, if something like this could be done, it would be really useful.

@nbouvrette It looks good, when I have more time I will try it and see how it is. And congratulations 😊

@westprophet is it happening also in [1.0.2-canary.8](https://github.com/vinissimus/next-translate/releases/tag/1.0.2-canary.8) prerelease?

@westprophet I leave the issue open to fix it for version 1.0.3

I hope this is the case @vimutti77!! 😊. @westprophet @zimenu if you can confirm it would be great.

And is it really necessary to use DynamicNamespace for this case? After login you can redirect to the same path with the lang changed and everything becomes much simpler.

You can use the [DynamicNamespaces](https://github.com/vinissimus/next-translate#dynamicnamespaces) component wrapped with a [I18nProvider](https://github.com/vinissimus/next-translate#i18nprovider) with the custom language. And you need to save this language in your way... (state / cookie / localstorage...) Ex:...

@vvo As a workaround try to add the prop `key={lang}` to I18Provider to force to remounting all the content (not just rerender). DynamicNamespaces right now is loading the namespaces only...