\n\n\n### Additional context\n\nAt runtime the locales array is properly available see console log :\n\n\u003Cimg width=\"574\" height=\"98\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a567197b-ed0e-477c-a908-3ce9b0e47c7d\" />\n\n### Logs\n\n```shell\n\n```",[3172],{"name":3173,"color":3174},"pending triage","c2e0c6",3834,"nuxt-modules","i18n","open","TS error: According to typeScript locales property is not exported by usei18n composable","2025-10-04T07:35:11Z","https://github.com/nuxt-modules/i18n/issues/3834",0.723918,{"description":3184,"labels":3185,"number":3187,"owner":3176,"repository":3177,"state":3178,"title":3188,"updated_at":3189,"url":3190,"score":3191},"### Describe the feature\n\nHi,\nBasically, I have a root `schedule.vue` page which is this route `/en/schedule`.\n\n\u003Cimg width=\"319\" height=\"128\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/03ec9ac3-c1ce-409c-869e-eb48888e241c\" />\n\nThe schedule page has nested \"child\" routes, which are displayed as \"tabs\" using `\u003CNuxtChild />`.\n\n\u003Cimg width=\"1288\" height=\"664\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3f1a9bac-7094-4cd6-b5a8-3b6f8d26069f\" />\n\nWhen I visit the schedule route, I want to redirected to `schedule/[day].vue`, with \"day\" param set as \"1\", which would display the schedule for the first day of the event `/en/schedule/1`.\n\nI had to create a custom middleware because it was not supported.\n```js\n// schedule.vue\n\ndefinePageMeta({\n localeRedirect: {\n name: 'schedule-day',\n params: { day: 1 },\n },\n i18n: {\n paths: {\n fr: '/programmation',\n en: '/schedule',\n },\n },\n});\n```\n\n```js\n// localeRedirect.global.ts\n\nexport default defineNuxtRouteMiddleware((to) => {\n const localePath = useLocalePath();\n if (to.meta.localeRedirect && to.matched.length === 1 && !to.redirectedFrom) {\n return navigateTo(localePath(to.meta.localeRedirect));\n }\n});\n```\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).",[3186],{"name":3173,"color":3174},3801,"Add i18n support to `redirect` inside `definePageMeta`","2025-08-31T09:50:36Z","https://github.com/nuxt-modules/i18n/issues/3801",0.75307226,{"description":3193,"labels":3194,"number":3199,"owner":3176,"repository":3177,"state":3178,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.17.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @pinia/nuxt@0.9.0, @nuxt/eslint@0.7.4, @nuxtjs/i18n@9.1.1\n- Build Modules: -\n------------------------------\n\n```ts\nexport default defineNuxtConfig({\n compatibilityDate: \"2024-11-01\",\n devtools: { enabled: true },\n\n modules: [\"@pinia/nuxt\", \"@nuxt/eslint\", \"@nuxtjs/i18n\"],\n i18n: {\n debug: true,\n types: 'composition',\n strategy: 'no_prefix',\n defaultLocale: 'en',\n lazy: true,\n langDir: 'locales',\n locales: [\n {\n name: 'English',\n code: 'en',\n language: 'en-GB',\n file: 'en-GB.json',\n },\n ],\n },\n\n future: {\n compatibilityVersion: 4,\n },\n```\n\n### Reproduction\n\nI don't know how reproduce this problem in online services\n\n### Describe the bug\n\nWith this configuration on a clean project I get this typing error: `'__VLS_ctx.$t' is of type 'unknown'.`\n\n\u003Cimg width=\"916\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/17be6c4d-fc51-4352-adc5-78db230f7ef0\" />\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3195,3196],{"name":3173,"color":3174},{"name":3197,"color":3198},"need reproduction","CD234A",3271,"[WebStorm] Type error '__VLS_ctx.$t' is of type 'unknown'.","2025-07-04T14:54:08Z","https://github.com/nuxt-modules/i18n/issues/3271",0.7531363,{"description":3205,"labels":3206,"number":3208,"owner":3176,"repository":3177,"state":3178,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Describe the feature\n\nCurrently, the files property in the locales configuration only supports an array of file paths. I would like to propose supporting a prefix option for each file to namespace its translations when loaded.\n```\ni18n: {\n locales: [\n {\n code: \"en\",\n name: \"English\",\n files: [\n { path: \"en/common.json\", prefix: \"common\" },\n { path: \"en/checkout.json\", prefix: \"checkout\" },\n { path: \"en/order.json\", prefix: \"order\" }\n ]\n }\n ]\n}\n```\nWith this configuration, the keys inside en/checkout.json would be accessible via t('checkout.key'), while en/common.json would be t('common.key'), and so on.\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).",[3207],{"name":3173,"color":3174},3593,"Support for file prefix in locales.files config","2025-05-11T07:15:31Z","https://github.com/nuxt-modules/i18n/issues/3593",0.7564908,{"description":3214,"labels":3215,"number":3216,"owner":3176,"repository":3177,"state":3178,"title":3217,"updated_at":3218,"url":3219,"score":3220},"I'm looking at replacing the vuetify locale as described [here](https://vuetifyjs.com/en/features/internationalization/#vue-i18n). As a result, I need to import the vuetify locale objects and add them to the messages from my app.\n\nI'm wondering if something like this is possible:\n```ts\n// i18n\\locales\\en.ts\nimport { en } from 'vuetify/locale'\n\nexport default {\n $vuetify: en,\n\n // my app messages\n errors: { },\n}\n```\n\nI have tried ^, and can't seem to get it working as the raw content is not resolved.\n\nIt looks like I have 2 solutions, but wanted to know if there was a better route:\n1. add messages to vue i18n config:\n```ts\n// i18n.config.ts\nimport { en } from 'vuetify/locale'\n\nexport default defineI18nConfig(() =>\n{\n console.log('here')\n return {\n messages: {\n en: {\n $vuetify: {\n ...en,\n },\n },\n },\n }\n})\n```\n\n2. make use of async `defineI18nLocale`\n```ts\n// i18n\\locales\\en.ts\nimport { en } from 'vuetify/locale'\n\nexport default defineI18nLocale(async (locale) =>\n return {\n $vuetify: en,\n \n // my app messages\n errors: { },\n }\n})\n```",[],3688,"Importing file inside a language file","2025-06-11T18:36:20Z","https://github.com/nuxt-modules/i18n/issues/3688",0.7597714,{"description":3222,"labels":3223,"number":3225,"owner":3176,"repository":3177,"state":3178,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.19.0\n- Nuxt Version: 4.0.2\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: modules, $development, $production, devtools, css, mdc, runtimeConfig, routeRules, experimental, compatibilityDate, nitro, vite, hooks, eslint, fonts, i18n, icon, image, shadcn, supabase, tiptap\n- Runtime Modules: @sentry/nuxt/module@9.42.1, @nuxtjs/color-mode@3.5.2, @nuxtjs/tailwindcss@7.0.0-beta.0, shadcn-nuxt@2.2.0, @nuxtjs/i18n@10.0.3, @nuxtjs/supabase@1.6.0, @nuxt/icon@1.15.0, @nuxt/eslint@1.7.1, nuxt-tiptap-editor@2.3.1, @nuxtjs/mdc@0.17.2, @vueuse/nuxt@13.6.0, @nuxt/image@1.10.0, @nuxt/fonts@0.11.4, nuxt-time@1.0.3, @nuxt/icon@1.15.0, @nuxtjs/leaflet@1.3.2\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/Chrissi2812/nuxt_bug_reports/tree/i18n/types-router\n--- Or ---\nhttps://stackblitz.com/edit/github-9m9yc3ub\n\n\u003Cimg width=\"502\" height=\"411\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f725bb5d-c55d-4200-b26b-8d76338624b0\" />\n\n### Describe the bug\n\nWith the default settings and `experimental.typedPages: true` the generated types are not correctly picked up.\n\nIf I rename `RouteNamedMapI18n` to `RouteNamedMap` the types are available.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3224],{"name":3173,"color":3174},3771,"useRoute needs suffix to work","2025-08-05T16:28:06Z","https://github.com/nuxt-modules/i18n/issues/3771",0.7609421,{"description":3231,"labels":3232,"number":3234,"owner":3176,"repository":3177,"state":3178,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Environment\n\nnuxt: 4.0.0\n@nuxtjs/i18n: 10.1.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-qmsm1tjo?file=app%2Fpages%2Ftest-page.vue\n\n### Describe the bug\n\nI want to use `localePath` by passing in a route and the default language to get a link based on the default language, but the locale parameter doesn’t seem to take effect. Instead, it returns a link according to the language of the given route. When switching between different languages, the printed output is as follows.\n\n```javascript\nconst route = useRoute();\nconst localePath = useLocalePath();\nconst { defaultLocale } = useI18n();\n\n// log: /test-page\nconst truePath = computed(() => {\n return localePath({ name: 'test-page' }, defaultLocale);\n});\n\n// log: /nl/test-page\nconst falsePathA = computed(() => {\n return localePath({ name: 'test-page___nl' }, defaultLocale);\n});\n\n// log: /test-page /nl/test-page /ja/test-page\nconst falsePathB = computed(() => {\n return localePath(route, defaultLocale);\n});\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\n\n```",[3233],{"name":3173,"color":3174},3840,"Passing the Locale parameter to useLocalePath does not return the expected result.","2025-10-10T12:56:45Z","https://github.com/nuxt-modules/i18n/issues/3840",0.76184916,{"description":3240,"labels":3241,"number":3246,"owner":3176,"repository":3177,"state":3247,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Environment\n\n- Operating System: Darwin\n- Node Version: v24.5.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.4\n- Package Manager: bun@1.2.20\n- Builder: -\n- User Config: modules, devtools, app, hooks, components, compatibilityDate, i18n, vite\n- Runtime Modules: @nuxt/eslint@1.8.0, @nuxt/test-utils/module@3.19.2\n- Build Modules: -\n\n(I am using a nuxt layer which configures the i18n module so I suspect that's the reason the module does not show up above)\n\n### Reproduction\n\nUnfortunately did not manage to create a reliable reproduction 😕\n\n### Describe the bug\n\nHello 👋,\n\nsince updating to the new version v10.0.4 I am having a problem with the i18n module. It seems the global `$t` instance is not available as I get the following error message: `ReferenceError: $t is not defined`.\n\nUnfortunately I wasn't able to create a minimal reproduction in stackblitz, so it must be something specific to my project that is causing this. Do you maybe have an idea what might be the issue or what I could check, based on the changes you did in v10.0.4?\n\nI am using the `$t` instance directly in my script setup block in a component and in there the error is thrown:\n```vue\n\u003Cscript setup lang=\"ts\">\n const test = computed(()=> $t('test'))\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cspan>{{ test }}\u003C/span>\n\u003C/template>\n```\n\nIs this an anti-pattern and the `useI18n` composable should be used instead? I was using the global `$t` instance directly since it saved a line of code and worked up to v10.0.3.\n\nI can't share the full project as it is work-related but here are some additional informations about my setup:\n- Nuxt layers: the i18n module is set-up in a \"core\" layer and all other layers and the main app extend from it\n- Multiple translation files: one i18n folder per layer with layer-specific translations\n- I am not using any `i18n.config.ts` files\n\nSorry for the non-existant repro and minimal info but maybe you have an idea what I could try. Thanks. 🙏\n\n### Additional context\n\n### package.json\n```\n{\n \"name\": \"a-project\",\n \"private\": true,\n \"type\": \"module\",\n \"engines\": {\n \"node\": \"22.x\"\n },\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"dev:host\": \"nuxt dev --host\",\n \"start\": \"node .output/server/index.mjs\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\",\n \"test\": \"vitest run\",\n \"test:coverage\": \"vitest run --coverage\",\n \"lint\": \"eslint .\",\n \"lint:fix\": \"eslint . --fix\",\n \"prettier\": \"prettier --write .\",\n \"typecheck\": \"nuxt typecheck\"\n },\n \"dependencies\": {\n \"@iconify-json/lucide\": \"^1.2.62\",\n \"@nuxt/image\": \"^1.11.0\",\n \"@nuxt/ui\": \"^3.3.0\",\n \"@nuxtjs/i18n\": \"10.0.4\",\n \"@samk-dev/nuxt-vcalendar\": \"^1.0.4\",\n \"@tanstack/vue-query\": \"^5.83.1\",\n \"@vueuse/core\": \"^13.6.0\",\n \"dayjs\": \"^1.11.13\",\n \"dayjs-nuxt\": \"^2.1.11\",\n \"nuxt\": \"^4.0.3\",\n \"nuxt-auth-sanctum\": \"^1.1.2\",\n \"nuxt-charts\": \"^0.2.3\",\n \"nuxt-viewport\": \"^2.3.1\",\n \"v-calendar\": \"^3.1.2\",\n \"vue\": \"^3.5.18\",\n \"vue-router\": \"^4.5.1\",\n \"zod\": \"^4.0.17\"\n },\n \"devDependencies\": {\n \"@nuxt/eslint\": \"^1.8.0\",\n \"@nuxt/test-utils\": \"^3.19.2\",\n \"@tanstack/eslint-plugin-query\": \"^5.83.1\",\n \"@types/node\": \"^24.2.1\",\n \"@vue/test-utils\": \"^2.4.6\",\n \"eslint\": \"^9.33.0\",\n \"eslint-config-prettier\": \"^10.1.8\",\n \"happy-dom\": \"^18.0.1\",\n \"prettier\": \"^3.6.2\",\n \"prettier-plugin-organize-imports\": \"^4.2.0\",\n \"prettier-plugin-tailwindcss\": \"^0.6.14\",\n \"typescript\": \"^5.9.2\",\n \"vitest\": \"^3.2.4\",\n \"vue-tsc\": \"^3.0.5\"\n },\n \"patchedDependencies\": {\n \"@samk-dev/nuxt-vcalendar@1.0.4\": \"patches/@samk-dev%2Fnuxt-vcalendar@1.0.4.patch\"\n }\n}\n```\n\n### nuxt.config.ts\n```ts\nexport default defineNuxtConfig({\n // ...,\n i18n: {\n locales: [\n { code: 'de', file: 'de.app.json' },\n { code: 'en', file: 'en.app.json' },\n ],\n defaultLocale: 'de',\n strategy: 'no_prefix',\n experimental: {\n typedOptionsAndMessages: 'default',\n },\n },\n})\n```\n\n### Logs\n\n```shell\n\n```",[3242,3243],{"name":3197,"color":3198},{"name":3244,"color":3245},"possible regression","B78041",3775,"closed","\"$t is not defined\" after updating to v10.0.4","2025-08-12T14:18:23Z","https://github.com/nuxt-modules/i18n/issues/3775",0.7260048,{"description":3253,"labels":3254,"number":3258,"owner":3176,"repository":3177,"state":3247,"title":3259,"updated_at":3260,"url":3261,"score":3262},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: devtools, app, modules, css, build, i18n, site, compatibilityDate\n- Runtime Modules: @nuxtjs/tailwindcss@6.13.2, @nuxt/image@1.9.0, @nuxtjs/i18n@9.5.3, @hypernym/nuxt-anime@2.1.1, @nuxtjs/sitemap@7.2.10, @nuxtjs/robots@5.2.9 \n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-yr15sl4p?file=locales%2Fen%2Findex.ts\n\n### Describe the bug\n\nI’m trying to auto-import all `.json` files in a ` locales/[lang]/` folder using `import.meta.glob` in each language’s `index.ts` file. This worked fine in Nuxt 2 using `require.context`, but in Nuxt 3 with` @nuxtjs/i18n`, I’m encountering the following error:\n\n`[plugin:vite:esbuild] Failed locale loading: 'unknown' type in **locales/ar/index.ts`**\n\n\n### Additional context\n\nWhat I’m Trying to Do\n```\n// locales/ar/index.ts\nconst modules = import.meta.glob('./**/*.json', { eager: true })\n\nconst messages: Record\u003Cstring, any> = {}\n\nfor (const path in modules) {\n const key = path\n .replace('./', '')\n .replace('.json', '')\n .replace(/\\//g, '.')\n messages[key] = modules[path].default\n}\n\nexport default messages\n```\n```\n// nuxt.config.ts\ni18n: {\n strategy: 'prefix_except_default',\n defaultLocale: 'ar',\n lazy: true,\n langDir: 'locales',\n locales: [\n { code: 'ar', name: 'Arabic', file: 'ar/index.ts' },\n { code: 'en', name: 'English', file: 'en/index.ts' }\n ]\n}\n```\n\nI expected Nuxt to allow ` import.meta.glob` usage in language-specific ` index.ts` files to auto-import and combine all locale messages from nested JSON files.\n\n**What Happened Instead**\n\nDynamic path template literals are not supported by Vite\n\nEven static `../locales/ar/**/*.json` fails due to path resolution issues\n\nErrors like `unknown type` or `Failed locale loading` appear\n\n\n**Workarounds Tried**\nUsing `require.context` – unsupported in Vite\n\nSwitching to manual static imports – works but violates DRY and doesn't scale\n\nMoving the glob loader to a utility file – still fails due to unresolved paths\n\nReplacing `lodash.set` with custom merging logic – no difference in behavior\n\nChecked paths, JSON validity, eager option – no effect\n\n### Logs\n\n```shell\n\n```",[3255],{"name":3256,"color":3257},"need more info","e295d6",3536,"Failed locale loading with static JSON imports in Nuxt 3","2025-05-23T10:27:57Z","https://github.com/nuxt-modules/i18n/issues/3536",0.73014814,{"description":3264,"labels":3265,"number":3266,"owner":3176,"repository":3177,"state":3247,"title":3267,"updated_at":3268,"url":3269,"score":3270},"## Bug Report\n\n### Describe the bug\nThe base locale file (ar.json) is completely ignored by @nuxtjs/i18n in Nuxt 4, while market-specific locale files (ar-MA.json, ar-SA.json, ar-AE.json) load correctly. This results in a broken fallback mechanism where translations that should fall back to the base locale display as literal translation keys.\n\n### Environment\n- **Nuxt**: 4.1.2\n- **@nuxtjs/i18n**: 10.1.0\n- **Node**: Latest LTS\n- **Package Manager**: pnpm\n- **OS**: macOS\n- **Browser**: All browsers (SSR issue)\n\n### Configuration\n\n**nuxt.config.ts (i18n section)**:\n```typescript\ni18n: {\n vueI18n: './i18n.config.ts',\n lazy: true,\n langDir: 'locales',\n defaultLocale: 'ar-ma',\n strategy: 'prefix',\n locales: [\n {\n code: 'ar',\n iso: 'ar',\n language: 'ar',\n file: 'ar.json',\n name: 'العربية',\n dir: 'rtl'\n },\n {\n code: 'ar-ma',\n iso: 'ar-MA',\n language: 'ar-MA',\n file: 'ar-MA.json',\n name: 'العربية',\n dir: 'rtl'\n },\n // ... other market locales (ar-sa, ar-ae)\n ]\n}\n```\n\n**i18n.config.ts**:\n```typescript\nexport default defineI18nConfig(() => ({\n legacy: false,\n fallbackLocale: 'ar',\n missingWarn: false,\n fallbackWarn: false\n}))\n```\n\n**File structure**:\n```\nlocales/\n├── ar.json (7KB - comprehensive base translations)\n├── ar-MA.json (12KB - Morocco-specific translations)\n├── ar-SA.json (1KB - Saudi Arabia-specific translations)\n└── ar-AE.json (1KB - UAE-specific translations)\n```\n\n### Expected Behavior\n1. When accessing `/ar-ma/` route, ar-MA.json should load first\n2. For missing keys in ar-MA.json, the system should fall back to ar.json\n3. All translation keys should resolve to actual translated text\n\n### Actual Behavior\n1. ✅ ar-MA.json loads correctly and provides market-specific translations\n2. ❌ ar.json is completely ignored and never loads\n3. ❌ Missing keys display as literal translation keys (e.g., \"nav.mainMenu\" instead of translated text)\n\n### Reproduction Steps\n1. Set up Nuxt 4 project with @nuxtjs/i18n v10.1.0\n2. Configure multiple locales with a base locale and market-specific locales\n3. Use `lazy: true` and `prefix` strategy\n4. Set `defaultLocale` to a market-specific locale (e.g., 'ar-ma')\n5. Set `fallbackLocale` to base locale (e.g., 'ar')\n6. Create comprehensive base locale file and minimal market-specific files\n7. Access market-specific route (e.g., `/ar-ma/`)\n8. Observe that base locale translations never load\n\n### Console Output\nThe server consistently shows warnings for ALL keys that should be in the base locale:\n```\nWARN [intlify] Not found 'nav.mainMenu' key in 'ar' locale messages.\nWARN [intlify] Not found 'search.title' key in 'ar' locale messages.\nWARN [intlify] Not found 'landing.hero.startConsultation' key in 'ar' locale messages.\n[... hundreds of similar warnings]\n```\n\n### Debugging Attempts\n1. ✅ Verified ar.json is valid JSON with correct structure\n2. ✅ Verified ar.json contains all the keys being requested\n3. ✅ Cleared .nuxt, .output, and node_modules/.cache multiple times\n4. ✅ Restarted dev server completely\n5. ✅ Added debug text to ar.json - changes are never reflected in output\n6. ✅ Confirmed file permissions and encoding are correct\n7. ❌ Base locale file is never loaded by the i18n system\n\n### Key Findings\n- **Market-specific locales work perfectly**: ar-MA.json loads and displays Morocco-specific translations\n- **Fallback logic works**: The system attempts to fall back to 'ar' locale (as shown in console warnings)\n- **Base locale completely ignored**: Despite being properly configured and containing valid translations, ar.json is never loaded\n- **File is valid**: ar.json parses correctly with node -e \"JSON.parse(...)\"\n\n### Minimal Reproduction\nThis appears to be related to the combination of:\n- Nuxt 4.1.2\n- @nuxtjs/i18n 10.1.0 \n- `lazy: true` configuration\n- `prefix` strategy\n- `defaultLocale` set to non-base locale\n- Multiple market-specific locales with base locale fallback\n\n### Impact\nThis breaks the core fallback functionality of internationalization, causing numerous UI elements to display as literal translation keys instead of translated text, significantly degrading user experience.\n\n### Workaround\nCurrently, the only workaround is to duplicate all base translations into each market-specific locale file, which defeats the purpose of having a fallback mechanism and creates maintenance overhead.",[],3824,"Base locale file not loading in Nuxt 4 with @nuxtjs/i18n v10.1.0 - Fallback mechanism partially broken","2025-10-08T13:11:01Z","https://github.com/nuxt-modules/i18n/issues/3824",0.7303214,["Reactive",3272],{},["Set"],["ShallowReactive",3275],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fcc1SS55f3NJ6mkjQpGy-MBLzuTk627Rb31iUhByslRQ":-1},"/nuxt-modules/i18n/3782"]