|\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).",[2881],{"name":2868,"color":2869},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.7322672,{"description":2888,"labels":2889,"number":2894,"owner":2871,"repository":2872,"state":2873,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Environment\n\nI am using @nuxtjs/i18n 9.5.4 with nuxt 3.17.3 for a statically generated website.\n\n\n### Reproduction\n\n-\n\n### Describe the bug\n\n\nIn nuxt.config.ts I have the default i18n settings:\n\n```\n\t\tdetectBrowserLanguage: {\n\t\t\tuseCookie: true,\n\t\t\tcookieKey: 'i18n_redirected',\n\t\t\tredirectOn: 'root'\n\t\t},\n```\n\nThe first time the site loads, before the i18n_redirected cookie exists, I see the following error in the console:\n\n```\nHydration completed but contains mismatches.\n```\n\nSubsequent visits to the site, once the cookie exists, do not have this error.\n\nI have confirmed that i18n locale detection is the issue by testing this configuration:\n\n```\n\t\tdetectBrowserLanguage: false\n```\n\nWhen detectBrowserLanguage is false, the issue does not occur.\n\nEDIT: Upon some further testing, the error only seems to occur if the browser locale that i18n matches is different from the defaultLocale. For example, if my browser locale is \"de\" but the i18n defaultLocale is \"en\" then the error will occur when i18n flips over to to the 'de' pages. By comparision, if the browser locale is \"en\", same as i18n defaultLocale, then the error will never occur. \n\nThe site renders fine, so it is not a big deal. But I'm wondering if there is anything that can be done to prevent that error from happening in the console on the initial load, before the cookie exists?\n\nThanks (in advance) for your help!\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[2890,2891],{"name":2868,"color":2869},{"name":2892,"color":2893},"need reproduction 💻","CD234A",3608,"Hydration mismatch on initial static site load, before i18n cookie is set","2025-05-21T00:33:31Z","https://github.com/nuxt-modules/i18n/issues/3608",0.74457586,{"description":2900,"labels":2901,"number":2905,"owner":2871,"repository":2872,"state":2906,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### 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_",[2902],{"name":2903,"color":2904},"switch locale","D2FCC6",2377,"closed","`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.63331765,{"description":2912,"labels":2913,"number":2915,"owner":2871,"repository":2872,"state":2906,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools, modules\n- Runtime Modules: @nuxtjs/i18n@9.3.1\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-8ekrd9jd?file=pages%2Fpage1.vue\n\n### Describe the bug\n\nIf `navigateTo(localePath('/'))` in useLazyAsyncData is called before the useLocalePath composable, navigation does not occur server side. In the reproduction, if you click the link to page1 in the header the navigation is there. However, if you type in /page1 manually in the container you will see that you actually land there and not get redirected to index.\n\nIf you move const localePath = useLocalePath() to a line before useLazyAsyncData, the redirect will perform as expected on server side as well.\n\nIn the current state it just does nothing -> no navigation and no error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[2914],{"name":2868,"color":2869},3405,"navigateTo(localePath()) in useLazyAsyncData does nothing","2025-05-23T13:35:42Z","https://github.com/nuxt-modules/i18n/issues/3405",0.6982386,{"description":2921,"labels":2922,"number":2926,"owner":2871,"repository":2872,"state":2906,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.6.2\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: build, css, devtools, modules, nitro, postcss, routeRules, runtimeConfig\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @nuxt/image@1.0.0-rc.1, nuxt-api-party@0.13.0, @nuxtjs/i18n@8.0.0-beta.13\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/joeykamsteeg/nuxt3-i18n-beforelocaleswitch-hook-not-working\n\n### Describe the bug\n\nThis hook should be triggered on app load (according to the documentation) and with initialSetup property we could hook our own logic how to handle URLs without locale in the URL. This is now not possible.\r\n\r\nIssue was reported earlier (#2248) but was closed without a resolution. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2923],{"name":2924,"color":2925},"hook","CF3B0A",2260,"Follow up: hook i18n:beforeLocaleSwitch does not use the locale that is return in the function","2025-05-22T19:39:58Z","https://github.com/nuxt-modules/i18n/issues/2260",0.6999203,{"description":2932,"labels":2933,"number":2939,"owner":2871,"repository":2872,"state":2906,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.11.1`\n- Nuxt Version: `3.13.2`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.9.7`\n- Package Manager: `npm@10.2.4`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxtjs/i18n@8.5.5`, `@pinia/nuxt@0.6.0`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-paob67?file=plugins%2Finit.ts but for some reason stackblitz not setting cookie when using setLocale from useI18n;\n\n### Describe the bug\n\nWhen calling window.location.reload() immediately in callback in\nnuxtApp.hook('i18n:localeSwitched'), cookie and current language resets to a previous value.\n\n```\nnuxtApp.hook('i18n:localeSwitched', () => window.location.reload());\n```\n\nBut if you wrap reload in setTimeout it works as expected\n\n```\nnuxtApp.hook('i18n:localeSwitched', () => {\n setTimeout(() => window.location.reload(), 100);\n});\n```\n\n### Additional context\n\nIf this hook is async we should probably wait for it and then execute our callback?\n\n### Logs\n\n_No response_",[2934,2937],{"name":2935,"color":2936},"scope: locales","006b75",{"name":2938,"color":2925},"scope: hooks",3192,"window.location.reload immediately after nuxtApp.hook('i18n:localeSwitched') not working as expected","2025-05-26T20:38:28Z","https://github.com/nuxt-modules/i18n/issues/3192",0.70377207,{"description":2945,"labels":2946,"number":2953,"owner":2871,"repository":2872,"state":2906,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### 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_",[2947,2950],{"name":2948,"color":2949},"🔨 p3-minor-bug","fbca04",{"name":2951,"color":2952},"scope: seo","30CDE0",2782,"Allow disabling page per locale with `useSetI18nParams`","2025-05-25T10:23:04Z","https://github.com/nuxt-modules/i18n/issues/2782",0.71073836,{"description":2959,"labels":2960,"number":2970,"owner":2871,"repository":2872,"state":2906,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@9.1.0, @pinia/nuxt@0.7.0\n- Build Modules: -\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-l8bdri?file=pages%2Ftest.vue,pages%2Findex.vue but it won't work in stackblitz so it needs to be reproduced in local environment\n\n### Describe the bug\n\nWhen using `\u003CNuxtLinkLocale>` with `to=\"/some-url-in-your-application\"` with `target=\"_blank\"`, locale prefix is not inserted in the resulting URL.\n\n### Additional context\n\nIn my opinion prefix should be added (or omitted if it is a default locale) as I use `\u003CNuxtLinkLocale>` here with exact purpose to direct to my application. Otherwise I would have used just an ordinary `\u003Ca>` tag or even `\u003CNuxtLink>`\n\n### Logs\n\n```shell\n\n```",[2961,2964,2967],{"name":2962,"color":2963},"bug 🐛","ee0701",{"name":2965,"color":2966},"PR Welcome","40922A",{"name":2968,"color":2969},"nuxt-link-locale","B327C3",3252,"NuxtLinkLocale with an attribute target=\"_blank\" does not respect the locale prefix","2025-05-22T15:26:02Z","https://github.com/nuxt-modules/i18n/issues/3252",0.71869063,{"description":2976,"labels":2977,"number":2979,"owner":2871,"repository":2872,"state":2906,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### 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```",[2978],{"name":2868,"color":2869},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.7193306,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwcOQfzyVQ3h6mMQXObfRnRKrJI-_8n0i4MnSroRmyVE":-1},"/nuxt-modules/i18n/3599"]