Skip to content

SSR

WARNING

This is mostly theoretical information. If you have feedback about i18next-vue in a SSR context, please let us know via a GitHub issue ❤️.

When using Server Side Rendering (SSR), i18next-vue makes sure to not introduce memory leaks. To do that, two i18next-vue features are not available on the server.

No component-specific messages

Neither <i18> blocks nor translations defined via i18nOptions.messages are supported. These are usually registered by i18next-vue with i18next in a Vue lifecycle hook and de-registered when the component is dismounted.

As there is no unmounted() life-cycle hook during SSR, we ignore these messages.

No rerenderOn updates

The rerenderOn plugin option is ignored on the server. The i18next instance needs to be properly set up with e.g. language and messages before rendering. Because of this, there is no need for such i18next reactivity.