|\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).",[2898],{"name":2899,"color":2900},"pending triage","c2e0c6",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.7411955,{"description":2907,"labels":2908,"number":2910,"owner":2868,"repository":2869,"state":2870,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.15.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, i18n, nitro\n- Runtime Modules: @nuxt/content@3.5.1, @nuxtjs/i18n@9.5.4\n- Build Modules: -\n\n\n### Reproduction\n\nA minimal reproduction of this issue can be found in the following repository: https://github.com/odan-sandbox/nuxt-content-and-i18n-no_prefix-example\n\n\n### Describe the bug\n\nWhen using the `no_prefix` strategy in `nuxt-i18n`, the locale detection based on the URL pathname is not functioning as expected. This results in incorrect locale assignment during SSR/SSG.\n\nFor example, accessing `/en/about` and `/ja/about` should render the corresponding locale-specific content, but instead, both paths are rendered using the default or server locale, ignoring the locale information in the pathname.\n\nThis issue causes problems for multilingual documentation sites using `nuxt/content`, where the content is structured by locale (e.g., `docs/en/about.md`, `docs/ja/about.md`). During SSG, both paths may be generated with the same language content, leading to incorrect output.\n\nIf a PR to resolve this issue is considered appropriate, I would be willing to work on it.\n\n\n### Additional context\n\nRelated: https://github.com/nuxt-modules/i18n/issues/3609\n\n### Logs\n\n```shell\n\n```",[2909],{"name":2899,"color":2900},3619,"Locale detection not working with `no_prefix` strategy","2025-05-19T06:13:27Z","https://github.com/nuxt-modules/i18n/issues/3619",0.76784605,{"description":2916,"labels":2917,"number":2924,"owner":2868,"repository":2869,"state":2925,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Discussed in https://github.com/nuxt-modules/i18n/discussions/2958\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **silgon** May 26, 2024\u003C/sup>\r\nI'm trying to build a multi-domain website. However, I want part of the languages to be on one site. I would like something like the following:\r\n\r\n```typescript\r\nexport default defineNuxtConfig({\r\n // ...\r\n\r\n i18n: {\r\n locales: [\r\n {\r\n code: 'en-US',\r\n domain: 'mydomain.com'\r\n },\r\n {\r\n code: 'es-MX',\r\n domain: 'mydomain.com/es-MX'\r\n },\r\n {\r\n code: 'ch-DE',\r\n domain: 'another-domain.ch'.\r\n },\r\n {\r\n code: 'ch-FR',\r\n domain: 'another-domain.ch/ch-FR'\r\n },\r\n ],\r\n differentDomains: true\r\n // Or enable the option in production only\r\n // differentDomains: (process.env.NODE_ENV === 'production')\r\n },\r\n\r\n // ...\r\n})\r\n```\r\n\r\nI hope that it's clear what I want to do given the configuration. My guidelines where the following link https://v8.i18n.nuxtjs.org/guide/different-domains\r\n\r\nCould somebody give me some guidance? I'm not able to do what I want. (also some insights in the sitemap with that kind of configuration would be cool, but not sure if this is the right place)\r\n\r\nWhen I'm in the same domain, the language does not change (I use the href configuration as specified in the documentation)\u003C/div>",[2918,2921],{"name":2919,"color":2920},"need more info","e295d6",{"name":2922,"color":2923},"scope: domains","fbca04",2979,"closed","Multi-Domain Website configuration with partial shared domains","2025-05-24T22:26:46Z","https://github.com/nuxt-modules/i18n/issues/2979",0.68206155,{"description":2931,"labels":2932,"number":2936,"owner":2868,"repository":2869,"state":2925,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.15.0`\n- Nuxt Version: `3.17.4`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `devtools`, `modules`, `i18n`, `compatibilityDate`, `app`\n- Runtime Modules: `@nuxtjs/i18n@9.5.4`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://github.com/cjpearson/switch-locale-path-repro\n\n### Describe the bug\n\nWhen using different domains for each locale, `switchLocalePath` will return an absolute URL for the current route in a different locale. However, if `app.baseURL` will not be included if it is set.\n\nFor example, calling `switchLocalePath` on `http://en.localhost/prefix/testing` will return `http://nl.localhost/testing`.\n\nThis is also the case when using path prefixes instead of domains, but less of an issue in practice since NuxtLink automatically adds the baseURL.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[2933,2934],{"name":2879,"color":2880},{"name":2935,"color":2923},"domain",3628,"`switchLocalePath` should include the baseURL","2025-05-22T15:50:22Z","https://github.com/nuxt-modules/i18n/issues/3628",0.68650234,{"description":2942,"labels":2943,"number":2950,"owner":2868,"repository":2869,"state":2925,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Describe the feature\n\nHi! I've a website with the following langs `it`, `de`, `en` and all the path in the translated lang have it's own path\r\n`/it/come-funziona`\r\n`/de/produkt`\r\n`/en/how-it-works`\r\n\r\nok, that's easy, I have de following config:\r\n```js\r\ndefineI18nRoute({\r\n locales: ['it', 'de', 'en'],\r\n\r\n paths: {\r\n it: '/come-funziona',\r\n de: '/produkt',\r\n en: '/how-it-works'\r\n }\r\n})\r\n```\r\n\r\nAnd if I have one less lang for a path it's something like: \r\n```js\r\ndefineI18nRoute({\r\n locales: ['it', 'en'],\r\n\r\n paths: {\r\n it: '/partner',\r\n en: '/partner'\r\n }\r\n})\r\n```\r\nOk, now the problem appear with dynamic pages. Because in the \"blog\" section not all articles are translated in all lang\r\n```js\r\ndefineI18nRoute({\r\n locales: ['it', 'en', 'de'],\r\n\r\n paths: {\r\n it: '/[blog]',\r\n en: '/[blog]',\r\n de: '/[blog]'\r\n }\r\n})\r\n\r\n// this specific article is not translated in `en`\r\nsetI18nParams({\r\n it: { blog: 'blog-1-it' },\r\n de: { blog: 'blog-1-de' },\r\n})\r\n```\r\n\r\nSo why is the following path added by default `/en/blog-1-it`? I think this behavior is similar to a bug. I don't want that to ever happen. Not even on non-dynamic pages\r\nI prefer something like\r\n```js\r\ndefineI18nRoute({\r\n paths: {\r\n it: '/partner',\r\n en: '/partner'\r\n }\r\n})\r\n```\r\nwithout having to specify the list of languages.\r\n\r\nBy default i have 3 langs, yes. And lang switcher always show 3 langs but if I don't set one it means that it doesn't exist, it makes no sense that only the `/en` prefix is changed and a route that doesn't exist is created.\r\nThis compromises the entire management of `rel=alternate` and SEO.\r\n\r\nI kindly ask you to give an answer to this question and look for a solution together because I think that the use of i18n is really complex if brought back to real management situations with a CMS.\r\nAfter almost a year of use there are still many problems related to SEO, changing languages, creating sitemaps, dynamic pages, etc.\r\n\r\nThank you very much\n\n### Additional information\n\n- [ ] 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).",[2944,2947],{"name":2945,"color":2946},"feature request","ffbb00",{"name":2948,"color":2949},"scope: seo","30CDE0",2784,"Remove the auto-complete alternate langs","2025-05-25T10:23:03Z","https://github.com/nuxt-modules/i18n/issues/2784",0.72249216,{"description":2956,"labels":2957,"number":2961,"owner":2868,"repository":2869,"state":2925,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@4.0.1\r\n- Builder: -\r\n- User Config: modules, i18n, devtools\r\n- Runtime Modules: @nuxtjs/i18n@8.1.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-c7te5q-s3x21p?file=app.vue\n\n### Describe the bug\n\nAlso if i've set \r\n```js\r\nsetI18nParams({\r\n it: { blog: 'blog-1-it' },\r\n de: { blog: 'blog-1-de' },\r\n en: { blog: undefined },\r\n})\r\n```\r\n\r\nthe `og:locale:alternate` for the `en` lang it was addes\r\n\r\n```html\r\n\u003Cmeta id=\"i18n-og-alt-en\" property=\"og:locale:alternate\" content=\"en\">\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2958,2960],{"name":2959,"color":2923},"🔨 p3-minor-bug",{"name":2948,"color":2949},2782,"Allow disabling page per locale with `useSetI18nParams`","2025-05-25T10:23:04Z","https://github.com/nuxt-modules/i18n/issues/2782",0.72330135,{"description":2967,"labels":2968,"number":2972,"owner":2868,"repository":2869,"state":2925,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.7.1\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: pnpm@8.6.12\r\n- Builder: -\r\n- User Config: extends, telemetry, ssr, fontMetrics, nitro, routeRules, runtimeConfig, build, modules, delayHydration, image, components, bugsnag, devtools, i18n, experimental, pwa, app, dnGraphqlClient, vite, plugins\r\n- Runtime Modules: @nuxtjs/fontaine@0.4.1, @pinia/nuxt@0.4.11, @nuxt/devtools@0.8.2, @vite-pwa/nuxt@0.1.0, nuxt-bugsnag@7.0.0, @digitalnatives/css-variables/nuxt@5.1.3, @digitalnatives/graphql-client@4.0.3, @nuxtjs/i18n@8.0.0-rc.4, @nuxt/image@1.0.0-rc.1, nuxt-delay-hydration@1.2.1, @digitalnatives/composables@2.0.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nA naïve reproduction is the following:\r\n\r\n```js\r\nconst route = useRoute(); \r\nconst locale = useLocale();\r\n\r\n// On switch, this will first log the NEW locale with the OLD path, then it will trigger a second time, logging the NEW locale with the NEW path\r\nwatchEffect(() => {\r\n console.log(route.fullPath);\r\n console.log(locale);\r\n});\r\n```\r\n\r\nAdd it to a global component in the layout that doesn't get mounted/umounted on URI change.\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nWhen using prefixed routes and a language switcher as described in the docs, it seems the locale changes before the route does.\r\n\r\nWhen watching the locale with `useAsyncData()` or `useLazyAsyncData()` this will cause the results of this call to be associated with the wrong URL/path, which then has a side-effect of refetching API data which was already pre-rendered in Nuxt static mode. Therefore, the pre-rendered payload is NOT used in this pattern, even though it should.\r\n\r\nI've also seen this lead to data mismatching to the wrong paths, but this is a bit harder to create a reproduction for.\r\n\r\n### Additional context\r\n\r\nMy current workaround is this;\r\n\r\ncomposable:\r\n```js\r\nexport const useVariables = () => {\r\n const route = useRoute();\r\n const { $i18n }: any = useNuxtApp();\r\n // Don't automatically update the site and url to ensure they both change at the same time\r\n variables.uri = toValue(route.path);\r\n variables.lang = toValue($i18n?.localeProperties)?.apiLanguageHandle;\r\n\r\n // Update variables manually when the route changes, at this point both the locale AND the URI are correct.\r\n watch(() => route.path, () => {\r\n variables.uri = toValue(route.path);\r\n variables.lang = toValue($i18n?.localeProperties)?.apiLanguageHandle;\r\n });\r\n return { variables };\r\n});\r\n```\r\n\r\nthen:\r\n\r\n```js\r\nconst { variables } = useVariables();\r\nuseAsyncData(() => { console.log('trigger!') } , { watch: [ variables ] });\r\n```\r\n\r\n\r\nPerhaps it would be possible to inject the locale & locale properties into the localized route meta? That way we could just watch the route and apply the language from that.\r\n\r\nRelates to #2278 \r\n\r\n### Logs\r\n\r\n_No response_",[2969],{"name":2970,"color":2971},"switch locale","D2FCC6",2377,"`locale` changes BEFORE the route path does, which causes issues with (static) `asyncData`-payloads","2025-05-16T11:44:11Z","https://github.com/nuxt-modules/i18n/issues/2377",0.7381154,{"description":2978,"labels":2979,"number":2981,"owner":2868,"repository":2869,"state":2925,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\n\n### Version\n \n```\n- nuxt : \"^3.12.4\",\n- nuxtjs/i18n@8.5.2 || nuxtjs/i18n@8.0.0-rc.3 \n```\n\n### i18n.config.ts\n```\nlazy: true,\nlangDir: 'locales',\nstrategy: 'prefix',\ndefaultLocale: 'en',\nfallbackLocale: 'en',\ndetectBrowserLanguage: {\n redirectOn: 'root'\n},\ncompilation: {\n strictMessage: false\n},\nlocales: [\n { code: 'en', file: 'en.json' },\n { code: 'es', file: 'es.json' },\n { code: 'fr', file: 'fr.json' },\n { code: 'de', file: 'de.json' }\n]\n```\n\n### Reproduction\n\nFor reproduce need to close tabs can't do it by stackblitz.\n\n### Describe the bug\n\n### Example:\n\n```\n1. Open localhost:3000/de, the cookie is set correctly: i18n_redirected=de.\n2. Close the tab.\n3. In a new tab, type localhost:3000/de in the address bar, but don’t hit Enter.\n4. Replace /de with /es, then delete /es and press Enter to navigate to localhost:3000.\n```\n\n### Result:\nIt redirects to `/es`, although `/de` is expected — because there was no actual navigation to `/es`, only manual editing of the address bar.\nThe same happens when selecting a URL from the browser’s dropdown history.\n\nThis causes issues: the browser often autofills URLs with old locales, and even a brief appearance of something like `localhost:3000/en` may change the locale. The user won’t return to their original locale `/de` unless they manually reselect it.\n\nThis behavior is non-obvious. I couldn’t find anything in the docs about change the locale by manual browser bar without transition. Changing the strategy isn’t an option — it's tightly coupled with SEO and app logic.\n\n### Expected behavior:\nLocale should change only after explicit navigation, `not just by typing or selecting a URL in the browser` without transition.\n\n### Question:\nIs this expected behavior? Is there any way to change it via configuration?\n\n### Additional context\n\nIt doesn’t matter that this happens on localhost or production.\n\n### Logs\n\n```shell\n\n```",[2980],{"name":2899,"color":2900},3591,"The locale changes without an actual navigation — just by typing the URL manually or selecting it from browser history.","2025-05-20T23:34:24Z","https://github.com/nuxt-modules/i18n/issues/3591",0.7473512,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEzHl-NDYQpJWLN4c41MuUWNEP4FyZI36_S398wY-rnc":-1},"/nuxt-modules/i18n/3053"]