Konstantin Koromyslo

to change locale with `differentDomains: true` the domain will change, page reload would happen in this case, realtime change of locale doesn't have sense in differentDomains mode.

Some managing translation services provide tools for in-context live translation edit. This is not my case, but just example of how this feature can be used https://docs.lokalise.com/en/articles/1592525-livejs-web-in-context-editor https://help.phrase.com/help/set-up-in-context-editor Also developing...

> Not anymore in latest versions. nuxtState is used to carry over server-loaded messages (when using lazy). There is one bug here, If I provide `defaultLocale` and load domain in...

I tried to: 1. set `messages` as `{"source": "nuxtConfig"}` in nuxt.config.js 2. call `setLocaleMessage` with `{ "source": "nuxtServerInit" }` in nuxtServerInit 3. call `setLocaleMessage` with `{ "source": "plugin" }` in...

You inspired me to test something. With `lazy: true` and empty file (`export default {}`), the behavior changed to ``` // server { source: "nuxtConfig" } { source: "plugin" }...

It doesn't run on the server. I meant if I will do this: ``` // nuxt.config.js modules: [ ["nuxt-i18n", { ..., locales: [ { code: "en-GB", } ], vueI18n: {...

The order of execution is 1. nuxt-i18n plugin server 2. nuxtServerInit server 3. nuxt-i18n plugin client `lazy: false` run `nuxt-i18n plugin client` with the state of $i18n set on `nuxt-i18n...

Sorry to step in. > I want (and that's how I think it should be) the app to be an immutable artifact. If I'm deploying the same app version at...

There is a workaround. I'm using **preview** token for all envs, and just keep version _draft/published_ in `publicRuntimeConfig` Per [docs](https://www.storyblok.com/docs/api/content-delivery): > To make the API as explorable as possible, accounts...

Consider using .env file for api keys https://github.com/nuxt-community/dotenv-module