|\u003Cimg width=\"324\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cd6f6927-33b3-4b85-a984-64c6cb1f53e5\" />|\n\n#### Proposed Feature: `localeDetector` Option\n\n##### Current Behavior Example\n\nTo illustrate the current behavior, consider the following scenario:\n\n* Accessing `/en/about` and `/ja/about` under the `no_prefix` strategy will not trigger locale detection based on the pathname.\n* As a result, both paths will use the language setting of the build machine during SSG, resulting in both paths potentially being generated in the same language.\n\nScreenshots and repository links demonstrating the current behavior will be provided to further clarify the issue.\n\nTo address this issue, I propose adding a new `localeDetector` option to the module configuration. This option allows specifying the methods for locale detection as follows:\n\n```typescript\ntype LocaleDetector = (\"pathname\" | \"domain\" | \"cookie\" | \"browser\")[];\n\nconst localeDetector: LocaleDetector = [\"pathname\", \"domain\", \"cookie\", \"browser\"];\n```\n\nIf `pathname` is specified, the locale will be automatically detected based on the URL pathname.\n\nThe default value of `localeDetector` will vary depending on the `strategy` value to maintain backward compatibility. For instance, when `no_prefix` is selected, the default value would be:\n\n```javascript\nlocaleDetector: [\"domain\", \"cookie\", \"browser\"]\n```\n\n##### Example Configuration for My Use Case:\n\n```javascript\nstrategy: \"no_prefix\",\nlocaleDetector: [\"pathname\", \"cookie\", \"browser\"]\n```\n\nThis configuration would resolve the issue by enabling locale detection based on pathname while maintaining backward compatibility with existing behavior.\n\nThank you for considering this feature request. I would be happy to provide further clarifications or contribute to the implementation if needed.\n\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution) (The contribution guideline of nuxt-modules/i18n is compliant with Nuxt too).\n- [x] Check existing [discussions](https://github.com/nuxt-modules/i18n/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3092],{"name":3020,"color":3021},3609,"Add `localeDetector` option to customize locale detection during Vue component rendering","2025-05-16T18:51:35Z","https://github.com/nuxt-modules/i18n/issues/3609",0.72378826,{"description":3099,"labels":3100,"number":3102,"owner":3026,"repository":3027,"state":3103,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v23.11.1\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.4.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, i18n, devServer\n- Runtime Modules: @nuxtjs/i18n@9.5.5\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nMinimal repo here https://github.com/ThibaudDauce/test_i18n\n\nThis is my `app.vue`:\n```html\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cp>{{ $t('Hello {name}', { name: 'John' }) }}\u003C/p>\n \u003Cp>{{ $t('The weather today is {condition}!', { condition: 'sunny' }) }}\u003C/p>\n \u003C/div>\n\u003C/template>\n```\n\nWith this `i18n/i18n.config.ts`:\n```ts\nexport default defineI18nConfig(() => {\n return {\n missingWarn: false,\n formatFallbackMessages: true,\n }\n})\n```\n\nAnd this `nuxt.config.ts`:\n```ts\nexport default defineNuxtConfig({\n compatibilityDate: '2025-05-15',\n devtools: { enabled: true },\n modules: ['@nuxtjs/i18n'],\n i18n: {\n defaultLocale: 'fr',\n },\n devServer: {\n port: 8080,\n },\n})\n```\n\n`missingWarn: false` is working so the config seems to be loaded correctly.\n\n### Describe the bug\n\nWhen I set `formatFallbackMessages: true`, the messages are not formatted in the template.\n",[3101],{"name":3020,"color":3021},3670,"closed","Cannot set `formatFallbackMessages`","2025-06-02T13:58:58Z","https://github.com/nuxt-modules/i18n/issues/3670",0.65914804,{"description":3109,"labels":3110,"number":3120,"owner":3026,"repository":3027,"state":3103,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Describe the feature\r\n\r\nAs discussed on Discord with @BobbieGoede and @harlan-zw, there is Harlan's amazing [site-config](https://nuxtseo.com/site-config/getting-started/background) project which aims to provide a central method for general site configuration so not every other module has to implement this itself.\r\n\r\n`nuxt-i18n` allows to specify a `baseUrl`, which is exactly such a reimplementation. I propose to support reading the `i18n.baseUrl` from `site.url` when it is available, keeping the fallback to `i18n.baseUrl`.\r\n\r\nOf course `i18n.baseUrl` *could* be marked as deprecated until the final `v8` release if everything works fine outsourcing the `baseUrl` to `nuxt-site-config` to keep a separation of concerns.\r\n\r\n### Additional information\r\n\r\n- [x] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution) (The contribution guideline of nuxt-modules/i18n is compliant with Nuxt too).\r\n- [X] Check existing [discussions](https://github.com/nuxt-modules/i18n/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3111,3114,3117],{"name":3112,"color":3113},"need discussion","E9EC2E",{"name":3115,"color":3116},"PR Welcome","40922A",{"name":3118,"color":3119},"scope: configuration","b60205",2474,"feat: support `nuxt-site-config`","2025-07-03T13:00:13Z","https://github.com/nuxt-modules/i18n/issues/2474",0.6683149,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMekXsFrV6Mv_KdsYj-a54AN0G6rM5Lz0WVVX6EghS98":-1},"/nuxt-modules/i18n/3596"]