\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/movie\" :title=\"$t('Movies')\" data-testid=\"movies-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-film-strip-fill text-primary' : 'i-ph-film-strip'\"\n />\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/tv\" :title=\"$t('TV Shows')\" data-testid=\"tv-shows-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-television-simple-fill text-primary' : 'i-ph-television-simple'\"\n />\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/search\" :title=\"$t('Search')\" data-testid=\"search-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-magnifying-glass-fill text-primary' : 'i-ph-magnifying-glass'\"\n />\n \u003C/NuxtLink>\n \u003C/div>\n\u003C/template>\n```\n\n`NavBar.nuxt.test.ts File`\n```\nimport type { VueWrapper } from '@vue/test-utils'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport { describe, expect, it } from 'vitest'\n\nimport NavBar from './NavBar.vue'\n\ndescribe('navBar', () => {\n it('renders Home link correctly', async () => {\n const wrapper = await mountSuspended(NavBar)\n\n // test true to be true\n expect(true).toBe(true)\n })\n```\n\n### Describe the bug\n\nIm trying to to a simple component test and I think it's failing to mock NuxtLink with slots when it is destruturing the property isActive\n\n### Additional context\n\n_No response_\n\n### Logs\n\nhttps://github.com/Archetipo95/movies/actions/runs/12358331784/job/34488575188?pr=2",[3019],{"name":3020,"color":3021},"pending triage","5D08F5",1042,"nuxt","test-utils","open","TypeError: Cannot destructure property 'isActive' of 'undefined' as it is undefined - NuxtLink","2024-12-16T17:53:11Z","https://github.com/nuxt/test-utils/issues/1042",0.46713004,{"description":3031,"labels":3032,"number":3035,"owner":3023,"repository":3023,"state":3025,"title":3036,"updated_at":3037,"url":3038,"score":3039},"### Describe the feature\n\nThe problem\n\nMany environments like Docker and Kubernetes provide secrets as files (e.g., /run/secrets/xxx). A common convention in these platforms is to define environment variables ending with _FILE, which point to files containing the actual secret values.\n\nNuxt currently does not support this convention natively.\n\nFor example:\n`TEST_SECRET_FILE=/run/secrets/app-secret`\n\nShould automatically populate:\n`process.env.TEST_SECRET`\n\nwith the contents of that file.\n\nThis pattern helps securely inject secrets without hardcoding them into the container or needing custom workarounds like entrypoint.sh scripts.\n\nProposed behavior\n\nNuxt should support resolving environment variables from files using a _FILE suffix convention. The logic could be:\n\n- For each process.env[KEY + \"_FILE\"], if the referenced file exists and is readable:\n- Populate process.env[KEY] with the file’s contents\n- Skip if process.env[KEY] is already explicitly set (i.e., the _FILE version acts as a fallback)\n\nThis approach mirrors standard behavior used in Docker Swarm, Kubernetes, and many CI/CD tools. \nThe variable names are flexible — either TEST_SECRET or TEST_SECRET_FILE may be used. If both are defined, TEST_SECRET takes precedence and the file-based value is ignored.\n\nThe idea also mention [here](https://github.com/nuxt/nuxt/issues/15366#issuecomment-2858874131).\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).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3033],{"name":3020,"color":3034},"E99695",32349,"Support _FILE environment variables for loading secrets from files","2025-06-09T11:45:30Z","https://github.com/nuxt/nuxt/issues/32349",0.76348346,{"description":3041,"labels":3042,"number":3049,"owner":3023,"repository":3050,"state":3025,"title":3051,"updated_at":3052,"url":3053,"score":3054},"### Description\n\nHello,\nAny events fired when month or year is changed? Are there any events emitted?\nCouldnt find anything in the docs\n\nthanks.",[3043,3046],{"name":3044,"color":3045},"question","d876e3",{"name":3047,"color":3048},"v3","49DCB8",3593,"ui","Calendar : Month / Year Emits","2025-03-21T18:11:05Z","https://github.com/nuxt/ui/issues/3593",0.7697046,{"description":3056,"labels":3057,"number":3061,"owner":3023,"repository":3024,"state":3025,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[3058],{"name":3059,"color":3060},"bug","d73a4a",684,"mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.76993775,{"labels":3067,"number":3074,"owner":3023,"repository":3023,"state":3075,"title":3076,"updated_at":3077,"url":3078,"score":3079},[3068,3071],{"name":3069,"color":3070},"enhancement","8DEF37",{"name":3072,"color":3073},"2.x","d4c5f9",9961,"closed","[ENV] Runtime variables actually configurable at runtime","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9961",0.75814766,{"description":3081,"labels":3082,"number":3084,"owner":3023,"repository":3023,"state":3075,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: future, app, vite, devServer, components, site, routeRules, modules, image, gtag, i18n, tailwindcss, icon, primevue, runtimeConfig, devtools, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@8.5.6, @nuxtjs/tailwindcss@6.13.1, @nuxt/image@1.9.0, nuxt-gtag@3.0.2, @vueuse/nuxt@12.4.0, @nuxtjs/seo@2.0.3, nuxt-primevue@3.0.0, @nuxt/eslint@0.7.5, @nuxt/icon@1.10.3, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n### Reproduction\n\nComplicated to reproduce as it happens in github actions and docker.\n\n### Describe the bug\n\nHi guys, \nI am building my app with Github Actions and in my repo I have set two env variables \"NUXT_PUBLIC_BACKEND_URL_INT\" and \"NUXT_PUBLIC_BACKEND_URL_EXT\", but they are not overridden and stay empty strings in runtime.\nDocker build step in my workflow yaml looks like this:\n``` yaml\n env:\n REPO_ID: *****\n NUXT_PUBLIC_BACKEND_URL_INT: ${{ vars.NUXT_PUBLIC_BACKEND_URL_INT }}\n NUXT_PUBLIC_BACKEND_URL_EXT: ${{ vars.NUXT_PUBLIC_BACKEND_URL_EXT }}\n steps:\n - name: Checkout repository\n uses: actions/checkout@v3\n\n - name: Get BUILD_SHA\n run: echo \"BUILD_SHA=$(echo $GITHUB_SHA | head -c7)\" >> $GITHUB_ENV\n\n - name: Build Docker image\n run: docker build --build-arg \"NUXT_PUBLIC_BACKEND_URL_INT=$NUXT_PUBLIC_BACKEND_URL_INT\" --build-arg \"NUXT_PUBLIC_BACKEND_URL_EXT=$NUXT_PUBLIC_BACKEND_URL_EXT\" -t cr4uhra3fp9d.azurecr.io/$REPO_ID:$BUILD_SHA .\n```\n\nThen in my Dockerfile, it looks like this:\n``` Dockerfile\nFROM node:22-slim AS build\n\nARG NUXT_PUBLIC_BACKEND_URL_INT\nARG NUXT_PUBLIC_BACKEND_URL_EXT\n\n# Enable pnpm\nENV PNPM_HOME=\"/pnpm\"\nENV PATH=\"$PNPM_HOME:$PATH\"\nRUN corepack enable\n\nWORKDIR /app\n\nCOPY ./package.json /app/\n\nRUN pnpm install --shamefully-hoist\n\nCOPY . ./\n\nENV NODE_OPTIONS=\"--max-old-space-size=4096\"\n\nENV NUXT_PUBLIC_BACKEND_URL_INT=$NUXT_PUBLIC_BACKEND_URL_INT\nENV NUXT_PUBLIC_BACKEND_URL_EXT=$NUXT_PUBLIC_BACKEND_URL_EXT\n\nRUN pnpm run build\n\n# --------------------\n\nFROM node:22-slim\n\nWORKDIR /app\n\nCOPY --from=build /app/.output ./\n\nENV NUXT_PUBLIC_BACKEND_URL_INT=$NUXT_PUBLIC_BACKEND_URL_INT\nENV NUXT_PUBLIC_BACKEND_URL_EXT=$NUXT_PUBLIC_BACKEND_URL_EXT\n\nEXPOSE 3000\nCMD [\"node\", \"/app/server/index.mjs\"]\n\n```\n\nand lastly nuxt.config.ts:\n```ts\nruntimeConfig: {\n public: {\n backendUrlExt: \"\",\n backendUrlInt: \"\",\n },\n },\n```\n\nI am deploying my app to MS Azure kubernetes cluster. When I have these env variables set in my local environment in .env file, it works correctly and also if I use Vercel and have them set in project environment variables. I also tried creating .env file directly inside Dockerfile (without success) like this:\n``` Dockerfile\nRUN cat \u003C\u003CEOF >> .env\n NUXT_PUBLIC_BACKEND_URL_INT=$NUXT_PUBLIC_BACKEND_URL_INT\n NUXT_PUBLIC_BACKEND_URL_EXT=$NUXT_PUBLIC_BACKEND_URL_EXT\nEOF\n\nRUN pnpm run build\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3083],{"name":3020,"color":3034},30605,"Dockerfile env variables don't override runtimeConfig using Github Actions","2025-03-05T10:14:56Z","https://github.com/nuxt/nuxt/issues/30605",0.76113695,{"description":3090,"labels":3091,"number":3097,"owner":3023,"repository":3050,"state":3075,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, components, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0, @pinia/nuxt@0.10.1, compodium@0.1.0-beta.5\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUInputMenu :items=\"idList\" v-model=\"value\" />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(0)\nconst idList = ref([168, 170, 203])\n\u003C/script>\n```\n\n### Description\n\nIf adding array of numbers to InputMenu the menu isn't closing after choosing a number.\nOnly way to close it is double-clicking on the dropdown arrow.\nThe Console shows an error in useFilter.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: string.normalize is not a function\n at contains (useFilter.js?v=87101672:23:21)\n at InputMenu.vue:114:18\n at wrappedFn (reactivity.esm-bundler.js?v=87101672:820:19)\n at Array.filter (\u003Canonymous>)\n at apply (reactivity.esm-bundler.js?v=87101672:828:27)\n at Proxy.filter (reactivity.esm-bundler.js?v=87101672:720:12)\n at InputMenu.vue:112:50\n at Array.map (\u003Canonymous>)\n at ComputedRefImpl.fn (InputMenu.vue:112:27)\n at refreshComputed (reactivity.esm-bundler.js?v=87101672:353:29)\n```",[3092,3093,3094],{"name":3059,"color":3060},{"name":3047,"color":3048},{"name":3095,"color":3096},"triage","ffffff",3606,"Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.7672361,{"description":3103,"labels":3104,"number":3105,"owner":3023,"repository":3106,"state":3075,"title":3107,"updated_at":3108,"url":3109,"score":3110},"In `v0.6.5` this works:\r\n\r\n```ts\r\nnuxtIcon: {\r\n aliases: {\r\n 'aws': 'IconAWS',\r\n // ...\r\n }\r\n}\r\n```\r\n\r\nif there is a component in global named `IconAWS.vue`, but in `v0.6.6` it breaks. The reason is the uppercase naming, if I rename the component and the alias to `IconAws.vue` it works.",[],125,"icon","v0.6.6 has problems with uppercase alias names","2023-12-24T15:42:29Z","https://github.com/nuxt/icon/issues/125",0.76904756,{"description":3112,"labels":3113,"number":3061,"owner":3023,"repository":3116,"state":3075,"title":3117,"updated_at":3118,"url":3119,"score":3065},"Blocked by #720 ",[3114],{"name":3069,"color":3115},"1ad6ff","nuxt.com","[Community] Nuxters filter to select community only","2022-07-25T13:34:54Z","https://github.com/nuxt/nuxt.com/issues/684",{"description":3121,"labels":3122,"number":3125,"owner":3023,"repository":3116,"state":3075,"title":3126,"updated_at":3127,"url":3128,"score":3129},"After updating the API, Jobs page is on error under certain circumstances : \n\nRelated commit : https://github.com/nuxtlabs/nuxt.com/commit/8962705b5d0dda99724d661efeeb4ed18e332db4\n\nEnvironment (Preview) : https://framework-p2aadzhns-nuxt-js.vercel.app/\n\n```\nTypeError: Cannot read properties of undefined (reading 'map')\n```\n\nThis is due to changes in the data structure of the API, changing from `\u003CNuxtJob[]>` to `{ data: \u003CNuxtJob[]>`. API endpoint (/api/jobs) seems to sometimes serve the outdated data.\n\n- 1 : client-side navigation from / to /support/jobs : fails\n- 2 : Server hit on /support/jobs : works\n- 3: client-side navigation back and forth to /support/jobs after 2 : works",[3123],{"name":3059,"color":3124},"ff281a",1041,"[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.77058107,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbaFADIin0yN40N0IwPDMVHi3rFniA0eJrB4zRcBd7S8":-1},"/nuxt/nuxt.com/1042"]