\n\n\u003Cimg width=\"1436\" height=\"474\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/378d9d5d-c5ae-48e5-a3b5-da94d168e206\" />\n\n### Describe the bug\n\n修改多语言热更新报错,\n\n\u003Cimg width=\"3318\" height=\"334\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ba25f21a-3216-4066-9e49-269efad06425\" />\n\n\u003Cimg width=\"1436\" height=\"474\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/378d9d5d-c5ae-48e5-a3b5-da94d168e206\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3018],{"name":3019,"color":3020},"pending triage","c2e0c6",3753,"nuxt-modules","i18n","open","在 nuxt4.0.2 里使用 \"@nuxtjs/i18n\": \"^10.0.2\" 热更新报错","2025-07-23T06:46:00Z","https://github.com/nuxt-modules/i18n/issues/3753",0.63030773,{"description":3030,"labels":3031,"number":3033,"owner":3022,"repository":3023,"state":3024,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v23.10.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.9\n- Builder: -\n- User Config: devtools, modules, i18n, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@9.5.5\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/warflash/nuxt-i18n-rolldown\n\n### Describe the bug\n\nBuilds are failing\n\n### Additional context\n\n[Rolldown vite was just announced as technical preview,](https://voidzero.dev/posts/announcing-rolldown-vite) so I wanted to jump in and test against our project. Dev works well, builds seem to fail, also on the i18n starter with the override applied.\n\nGiven that vite-rolldown aims to be a drop in replacement it might just need time for the vite team to iron out the cause of this bug. Just wanted to raise the issue in case it's some internal tooling in the i18n project that won't be compatible with vite in the future.\n\n### Logs\n\n```shell\n> nuxt build\n\n[nuxi 21:06:47] Nuxt 3.17.4 with Nitro 2.11.12\n\n[@nuxtjs/i18n 21:06:48] WARN bundle.optimizeTranslationDirective is enabled by default, we recommend disabling this feature as it causes issues and will be deprecated in v10.\nExplicitly setting this option to true or false disables this warning, for more details see: https://github.com/nuxt-modules/i18n/issues/3238#issuecomment-2672492536\n\n[nuxi 21:06:48] ℹ Building for Nitro preset: node-server\n[21:06:51] ℹ Building client...\n\n[21:06:51] WARN You have set optimizeDeps.esbuildOptions but this options is now deprecated. Vite now uses Rolldown to optimize the dependencies. Please use optimizeDeps.rollupOptions instead.\n\n[21:06:51] ℹ rolldown-vite v6.3.14 building for production...\n[21:06:52] ℹ ✓ 181 modules transformed.\n\n[21:06:52] ERROR ✗ Build failed in 531ms\n\n\n[nuxi 21:06:52] ERROR Nuxt Build Error: Build failed with 3 errors:\n\n[PARSE_ERROR] Error: Unexpected token\n ╭─[ i18n/locales/en.json:1:1 ]\n │\n 1 │ const resource = {\n │ ──┬── \n │ ╰──── \n───╯\n\n[PARSE_ERROR] Error: Unexpected token\n ╭─[ i18n/locales/nl.json:1:1 ]\n │\n 1 │ const resource = {\n │ ──┬── \n │ ╰──── \n───╯\n\n[PARSE_ERROR] Error: Unexpected token\n ╭─[ i18n/locales/ja.json:1:1 ]\n │\n 1 │ const resource = {\n │ ──┬── \n │ ╰──── \n───╯\n\n\n at normalizeErrors (/project/node_modules/.pnpm/rolldown@1.0.0-beta.10-commit.ac4e5db/node_modules/rolldown/dist/shared/src-r81e2JxS.mjs:2195:18)\n at handleOutputErrors (/project/node_modules/.pnpm/rolldown@1.0.0-beta.10-commit.ac4e5db/node_modules/rolldown/dist/shared/src-r81e2JxS.mjs:3125:34)\n at transformToRollupOutput (/project/node_modules/.pnpm/rolldown@1.0.0-beta.10-commit.ac4e5db/node_modules/rolldown/dist/shared/src-r81e2JxS.mjs:3119:2)\n at RolldownBuild.write (/project/node_modules/.pnpm/rolldown@1.0.0-beta.10-commit.ac4e5db/node_modules/rolldown/dist/shared/src-r81e2JxS.mjs:4269:10)\n at async buildEnvironment (/project/node_modules/.pnpm/rolldown-vite@6.3.14_esbuild@0.25.5_jiti@2.4.2/node_modules/rolldown-vite/dist/node/chunks/dep-C0xpd56d.js:44464:16)\n at async buildClient (/project/node_modules/.pnpm/@nuxt+vite-builder@3.17.4_eslint@9.27.0_rollup@4.41.1_typescript@5.8.3_vue@3.5.16/node_modules/@nuxt/vite-builder/dist/shared/vite-builder.DNPjFC0L.mjs:765:5)\n at async bundle (/project/node_modules/.pnpm/@nuxt+vite-builder@3.17.4_eslint@9.27.0_rollup@4.41.1_typescript@5.8.3_vue@3.5.16/node_modules/@nuxt/vite-builder/dist/shared/vite-builder.DNPjFC0L.mjs:1527:3)\n at async bundle (/project/node_modules/.pnpm/nuxt@3.17.4_eslint@9.27.0_rolldown-vite@6.3.14_rollup@4.41.1_typescript@5.8.3/node_modules/nuxt/dist/shared/nuxt.Ipy8-4AT.mjs:7387:5)\n at async build (/project/node_modules/.pnpm/nuxt@3.17.4_eslint@9.27.0_rolldown-vite@6.3.14_rollup@4.41.1_typescript@5.8.3/node_modules/nuxt/dist/shared/nuxt.Ipy8-4AT.mjs:7247:3)\n at async Object.run (/project/node_modules/.pnpm/@nuxt+cli@3.25.1/node_modules/@nuxt/cli/dist/chunks/build.mjs:74:5)\n```",[3032],{"name":3019,"color":3020},3659,"Builds with rolldown-vite + nuxt i18n fail","2025-05-30T19:14:35Z","https://github.com/nuxt-modules/i18n/issues/3659",0.67443454,{"description":3039,"labels":3040,"number":3042,"owner":3022,"repository":3023,"state":3024,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.12.0\n- Nuxt Version: 4.0.1\n- CLI Version: 3.26.4\n- Nitro Version: 2.12.4\n- Package Manager: npm@11.1.0\n- Builder: -\n- User Config: modules, imports, devtools, app, css, router, site, colorMode, runtimeConfig, generate, dev, compatibilityDate, nitro, debug, eslint, i18n, ogImage, robots, security, vuefire\n- Runtime Modules: @nuxt/ui@3.2.0, @nuxt/eslint@1.7.0, @nuxtjs/seo@3.1.0, @nuxtjs/i18n@10.0.2, nuxt-security@2.3.0, nuxt-vuefire@1.1.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nThe problem starts to appear after updating to nuxt-i18n v10 module\n\nWhat we can do to replicate:\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-dwb5kaqj?file=nuxt.config.ts\n\n### Describe the bug\n\nAfter updating i19n from version 9.5.6 to 10.0.2 I receive the following error on startup\n\n```\n[16:02:12] ERROR [request error] [unhandled] [GET] http://localhost:3000/__nuxt_error?error=true&url=%2Fdashboard&statusCode=500&statusMessage=Internal+Server+Error&message=(0%2C+__vite_ssr_import_0__.getApps)+is+not+a+function&stack=(0%2C+__vite_ssr_import_0__.getApps)+is+not+a+function%0Aat+ensureAdminApp+(/project/node_modules/vuefire/dist/server/index.mjs:42:17)%0Aat+/project/node_modules/nuxt-vuefire/dist/runtime/admin/plugin.server.js:13:62)%0Aat+/project/node_modules/nuxt/dist/app/nuxt.js:142:40)%0Aat+fn+(/project/node_modules/nuxt/dist/app/nuxt.js:220:36)%0Aat+Object.callAsync+(/project/node_modules/unctx/dist/index.mjs:72:47)%0Aat+/project/node_modules/nuxt/dist/app/nuxt.js:225:52)%0Aat+Object.runWithContext+(/project/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4020:18)%0Aat+callWithNuxt+(/project/node_modules/nuxt/dist/app/nuxt.js:225:24)%0Aat+/project/node_modules/nuxt/dist/app/nuxt.js:61:41)%0Aat+EffectScope.run+(/project/node_modules/@vue/reactivity/dist/reactivity.cjs.js:97:16)\n\nℹ Error: _ctx.$t is not a function\n\n ⁃ at _sfc_ssrRender (/project/components/Navigation.vue:175:15)\n\n 171 ┃ \u003CUButton\n 172 ┃ variant=\"ghost\"\n 173 ┃ :aria-label=\"item.label\"\n 174 ┃ >\n ❯ 175 ┃ \u003CUIcon :name=\"item.icon\" />\n 176 ┃ {{ item.label }}\n 177 ┃ \u003C/UButton>\n\n ⁃ at renderComponentSubTree (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:737:9) \n ⁃ at renderComponentVNode (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:686:12) \n ⁃ at ssrRenderComponent (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:100:10) \n ⁃ at _sfc_ssrRender (/project/layouts/default.vue:28:41) \n ⁃ at renderComponentSubTree (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:737:9) \n ⁃ at renderVNode (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:801:14) \n ⁃ at callWithNuxt (/project/node_modules/nuxt/dist/app/nuxt.js:225:24)\n\n[CAUSE]\nTypeError {\n message: '_ctx.$t is not a function',\n stack: '_ctx.$t is not a function\\n' +\n 'at _sfc_ssrRender (/project/components/Navigation.vue:175:15)\\n' +\n 'at renderComponentSubTree (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:737:9)\\n' +\n 'at renderComponentVNode (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:686:12)\\n' +\n 'at ssrRenderComponent (/project/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:100:10)\\n' +\n 'at _sfc_ssrRender (/project/layouts/default.vue:28:41)\\n' +\n '...'\n}\n```\n\n\nHence I can't start the whole application.\n\nI tried to reproduce it in the stackblitz, but all works fine there. Maybe it has something to do with my envirnoment as I deleted all .nuxt files and also removed all node modules/reinstalled them\n\n\n### Additional context\n\n\nAlso I have a previous error which then causes the application to crash:\n```\n WARN [Vue warn]: Property \"$t\" was accessed during render but is not defined on instance. 14:28:44 \n at \u003CHeaderBar>\n at \u003CDefault ref=Ref\u003C undefined > >\n at \u003CAsyncComponentWrapper ref=Ref\u003C undefined > >\n at \u003CLayoutLoader key=\"default\" layoutProps={\n ref: RefImpl {\n dep: Dep {\n computed: undefined,\n version: 0,\n activeLink: undefined,\n subs: undefined,\n map: undefined,\n key: undefined,\n sc: 0,\n __v_skip: true,\n subsHead: undefined\n },\n __v_isRef: true,\n __v_isShallow: true,\n _rawValue: undefined,\n _value: undefined\n }\n } name=\"default\" >\n at \u003CNuxtLayoutProvider layoutProps={\n ref: RefImpl {\n dep: Dep {\n computed: undefined,\n version: 0,\n activeLink: undefined,\n subs: undefined,\n map: undefined,\n key: undefined,\n sc: 0,\n __v_skip: true,\n subsHead: undefined\n },\n __v_isRef: true,\n __v_isShallow: true,\n _rawValue: undefined,\n _value: undefined\n }\n } key=\"default\" name=\"default\" ... >\n at \u003CNuxtLayout>\n at \u003CError error=(0 , __vite_ssr_import_0__.getApps) is not a function\n\n at ensureAdminApp (/app/node_modules/vuefire/dist/server/index.mjs:36:41)\n at /app/node_modules/nuxt-vuefire/dist/runtime/admin/plugin.server.js:12:68\n at /app/node_modules/nuxt/dist/app/nuxt.js:156:60\n at fn (/app/node_modules/nuxt/dist/app/nuxt.js:233:44)\n at Object.callAsync (/app/node_modules/unctx/dist/index.mjs:68:55)\n at /app/node_modules/nuxt/dist/app/nuxt.js:236:56\n at Object.runWithContext (/app/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4002:18)\n at callWithNuxt (/app/node_modules/nuxt/dist/app/nuxt.js:236:24)\n at /app/node_modules/nuxt/dist/app/nuxt.js:55:41\n at EffectScope.run (/app/node_modules/@vue/reactivity/dist/reactivity.cjs.js:85:16) >\n at \u003CNuxtRoot>\n\n[nuxt-app] vue:error: 9.872ms 14:28:44 \n[nuxt-app] app:error: 0.022ms 14:28:44 \n[nitro-runtime] error: 0.571ms\n```\n\nWhen I remove nuxt-vuefire. It works again, no error on startup.\n\nWhen I downgrade to 9.5.6 for the i18n module, it works too even with nuxt-vuefire and even with it throwing an error directly\n\n### Logs\n\n```shell\n\n```",[3041],{"name":3019,"color":3020},3755,"_ctx.$t is not a function","2025-07-23T13:58:47Z","https://github.com/nuxt-modules/i18n/issues/3755",0.69036275,{"description":3048,"labels":3049,"number":3051,"owner":3022,"repository":3023,"state":3024,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: modules, devtools, nitro, i18n\n- Runtime Modules: @nuxtjs/i18n@9.5.5-29143926.54460af\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-b5evupp3?file=nuxt.config.ts\n\n### Describe the bug\n\nWhen the site is generated or pre-rendered in `strategy: 'prefix'`, Browser language detection is not performed but the site always lands on the `defaultLocale` (`ja` in this case).\nThis is a bug present in both `V9` and `V10` and it would be nice to be fixed before the final release.\n\nCurrently the only solution I have found is to specify not to pre-render the `/` page and to start from the others (by the way it is not correct that this page is prerendered in `strategy: 'prefix'`):\n```js \n routeRules: {\n '/': {\n prerender: false,\n },\n '/ja': {\n prerender: true,\n },\n '/it': {\n prerender: true,\n },\n '/en': {\n prerender: true,\n },\n },\n```\n\n### Additional context\n\nI noticed this error when deploying to Netlify, but you can reproduce it with\n`nuxt build`\n`nuxt preview`\n\n### Logs\n\n```shell\n\n```",[3050],{"name":3019,"color":3020},3678,"Browser language detection on prerendering with `strategy: 'prefix'`","2025-06-05T15:21:38Z","https://github.com/nuxt-modules/i18n/issues/3678",0.6978038,{"description":3057,"labels":3058,"number":3063,"owner":3022,"repository":3023,"state":3024,"title":3064,"updated_at":3065,"url":3066,"score":3067},"### 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```",[3059,3060],{"name":3019,"color":3020},{"name":3061,"color":3062},"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.70611,{"description":3069,"labels":3070,"number":3072,"owner":3022,"repository":3023,"state":3024,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v21.7.1`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.9`\n- Package Manager: `npm@10.9.0`\n- Builder: `-`\n- User Config: `codegen`, `compatibilityDate`, `css`, `device`, `devtools`, `i18n`, `image`, `modules`, `runtimeConfig`, `scripts`, `srcDir`, `svgo`, `vite`, `watch`\n- Runtime Modules: `@bootstrap-vue-next/nuxt@0.29.3`, `@nuxt/eslint@1.3.0`, `@nuxt/fonts@0.11.2`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.6`, `@nuxtjs/device@3.2.4`, `@nuxtjs/i18n@9.5.3`, `@nuxtjs/stylelint-module@5.2.1`, `nuxt-svgo@4.0.19`, `nuxt-swiper@2.0.0`\n- Build Modules: `-`\n\n\n### Reproduction\n\nHere is the reproduction:\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-rskcxctd\n\n### Describe the bug\n\nWhen you translate your pages with defineI18nRoute (or maybe into `pages` key into i18n config) is getting rid when strategy in no prefixed (bot _no_prefix_ and _prefix_except_default_)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3071],{"name":3019,"color":3020},3598,"defineI18nRoute is not working with no_prefix strategy","2025-05-13T14:21:14Z","https://github.com/nuxt-modules/i18n/issues/3598",0.71633315,{"description":3078,"labels":3079,"number":3081,"owner":3022,"repository":3023,"state":3082,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Environment\n\nNuxt 4\nnew Typescript project references\ni18n 10.0.0-rc.3\n\n### Reproduction\n\nWill be given if requested.\n\n### Describe the bug\n\nApplying the new typescript project references typing in Nuxt 4 changes something about how types are resolved for the `i18n` key in `nuxt.config.ts`.\n\nWith old type setup, also Nuxt 4, the type is resolved to `.playground/.nuxt/types` in my project to something shown as:\n\n\u003Cimg width=\"505\" height=\"274\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1998c736-a15a-431a-ac9b-fb7e6193d553\" />\n\nWith the new type layout, the type resolves to `@nuxtjs/i18n/dist/module.d.mts`:\n\n\u003Cimg width=\"983\" height=\"247\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/953bab0d-12a9-4001-aab0-68a59b7eca08\" />\n\nOr:\n\n```ts\ninterface ModulePublicRuntimeConfig {\n i18n: I18nPublicRuntimeConfig;\n}\n```\n\nMy guess is that the code should be this instead:\n\n```ts\ninterface ModulePublicRuntimeConfig {\n i18n: Partial\u003CI18nPublicRuntimeConfig>;\n}\n```\n\nAlternatively, all keys on `I18nPublicRuntimeConfig` could get a suffix `?` to mark them key-optional.\n\n### Additional context\n\nI added https://github.com/nuxt-modules/i18n/pull/3730 which includes the first solution given.\n\n### Logs\n\n```shell\n\n```",[3080],{"name":3019,"color":3020},3729,"closed","fix(v10): `runtimeConfig` type in Nuxt 4","2025-07-17T08:39:49Z","https://github.com/nuxt-modules/i18n/issues/3729",0.67828274,{"description":3088,"labels":3089,"number":3091,"owner":3022,"repository":3023,"state":3082,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Environment\n\n**Module version:** \n`@nuxtjs/i18n` version: `^9.4.0`\n\n**Nuxt version:** \n`Nuxt 3.16.2`\n\n### ❗ Problem\n\nAfter building CI/CD pipeline of project, the generated `nuxt.i18n.options.mjs` includes **absolute paths** to the locale files, for example:\n\n```js\n{\n path: \"/home/gitlab-runner/builds/QEWN8sP-g/0/client/i18n/locales/ru/errors.json\",\n cache: undefined\n}\n```\n\n### Reproduction\n\nConfigure @nuxtjs/i18n in nuxt.config.ts:\n\n```\ni18n: {\n locales: [\n { code: 'ru', file: 'ru/errors.json' },\n { code: 'ro', file: 'ro/errors.json' },\n ],\n langDir: 'i18n/locales/',\n defaultLocale: 'ru',\n}\n```\n\nRun nuxt build\n\nInspect the contents of .output/public/_nuxt/ or nuxt.i18n.options.mjs\n\nNotice absolute paths included in the files array\n\n💡 Workarounds tried\n\n✅ fullInstall: false → no effect\n\n✅ Using relative langDir and file values → still resolves to absolute paths\n\n✅ Changing build environment → problem persists\n\n### Describe the bug\n\nPlease avoid emitting absolute file paths into the build output. Relative or virtualized paths would ensure cleaner builds, better security, and fewer environment-specific artifacts.\n\nLet me know if you need a minimal reproduction repo or additional logs.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3090],{"name":3019,"color":3020},3742,"Absolute file paths included in production bundle","2025-07-21T08:55:25Z","https://github.com/nuxt-modules/i18n/issues/3742",0.68340683,{"description":3097,"labels":3098,"number":3105,"owner":3022,"repository":3023,"state":3082,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: modules, devtools, app, css, runtimeConfig, future, compatibilityDate, vite, postcss, eslint, i18n, image, prismic\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxtjs/prismic@4.1.0, @nuxt/fonts@0.11.0, @nuxtjs/i18n@9.3.1, @nuxt/image@1.9.0, @vueuse/nuxt@13.0.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-w8n5eqto?file=pages%2Findex.vue\n\n### Describe the bug\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3099,3102],{"name":3100,"color":3101},"🍰 p2-nice-to-have","0e8a16",{"name":3103,"color":3104},"scope: components","B327C3",3402,"Double nested `NuxtLinkLocale`","2025-05-30T19:25:27Z","https://github.com/nuxt-modules/i18n/issues/3402",0.6865612,{"description":3111,"labels":3112,"number":3114,"owner":3022,"repository":3023,"state":3082,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### 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",[3113],{"name":3019,"color":3020},3670,"Cannot set `formatFallbackMessages`","2025-06-02T13:58:58Z","https://github.com/nuxt-modules/i18n/issues/3670",0.69135594,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f08mqB5JroUaybfmvv3QldU2mOmyVoAUEYfxvkylvaAk":-1},"/nuxt-modules/i18n/3731"]