\n\n### Description\n\nThe UInputTag element does not correctly render the error text for schema validation errors for pattern matching of the individual items within its array. \n\nIt works fine showing an error about the length of the array, but not about problems for the items within the array.\n\n\u003Cimg width=\"779\" height=\"328\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cf031108-314b-4fd5-9859-cd275b8d3410\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3172,3175,3178],{"name":3173,"color":3174},"bug","d73a4a",{"name":3176,"color":3177},"v3","49DCB8",{"name":3179,"color":3180},"triage","ffffff",4573,"nuxt","ui","open","UInputTag does not display validation errors for pattern matching","2025-07-22T14:39:33Z","https://github.com/nuxt/ui/issues/4573",0.733126,{"description":3190,"labels":3191,"number":3200,"owner":3182,"repository":3183,"state":3201,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.9.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.0\n- Nitro Version: 2.11.8\n- Package Manager: bun@1.2.9\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, runtimeConfig, css, app, ui, icon, fonts, image, nitro, i18n\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxt/image@1.10.0, @nuxt/scripts@0.11.5, @nuxtjs/i18n@9.4.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.2\n\n### Reproduction\n\n```vue\n\u003Cscript setup>\nconst items = [\n \"https://picsum.photos/468/468?random=1\",\n \"https://picsum.photos/468/468?random=2\",\n \"https://picsum.photos/468/468?random=3\",\n \"https://picsum.photos/468/468?random=4\",\n \"https://picsum.photos/468/468?random=5\",\n \"https://picsum.photos/468/468?random=6\",\n];\n\u003C/script>\n\u003Ctemplate>\n\u003CUCarousel\n v-slot=\"{ item }\"\n wheel-gestures\n class-names\n :items=\"items\"\n :ui=\"{\n item: 'basis-1/2 [&.is-snapped+*]:basis-1/3 [&.is-snapped+*+*]:basis-1/6',\n }\"\n align=\"start\"\n >\n \u003Cimg :src=\"item\" class=\"w-full h-auto\" />\n \u003C/UCarousel>\n\u003C/template>\n```\n\n### Description\n\nSimulate the behavior of https://m3.material.io/components/carousel/overview, Carousel will repeatedly calculate is-snapped in an infinite loop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3192,3193,3194,3195,3198],{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3179,"color":3180},{"name":3196,"color":3197},"closed-by-bot","ededed",{"name":3199,"color":3197},"stale",3883,"closed","[Carousel] Unable to differentiate item sizes","2025-08-12T02:12:47Z","https://github.com/nuxt/ui/issues/3883",0.6587616,{"description":3207,"labels":3208,"number":3214,"owner":3182,"repository":3183,"state":3201,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.2, @nuxtjs/seo@2.0.2, @nuxtjs/plausible@1.2.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.9\n\n### Reproduction\n\nOn a brand new project:\n\n```\nnpx nuxi@latest init my-app\ncd my-app\nnpm install @nuxt/ui@next\n```\n\nThen\n/app/app.vue\n```vue\n\u003Ctemplate>\n\t\u003CNuxtLayout>\n\t\t\u003CNuxtPage />\n\t\u003C/NuxtLayout>\n\u003C/template>\n```\n\nnuxt.config.ts\n```js\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n\tcompatibilityDate: \"2024-11-01\",\n modules: ['@nuxt/ui', '@nuxt/eslint', '@nuxtjs/seo'],\n css: ['~/assets/css/main.css'],\n\n\tdevtools: { enabled: true },\n\tfuture: {\n\t\tcompatibilityVersion: 4,\n\t},\n\tui: {\n // error here\n\t\tcolorMode: false,\n\t},\n});\n\n```\n\n### Description\n\nWhen changing the ui.colorMode to false AND using the `pages` folder, it crashes the whole app (error below).\n\n\n```\n500\n[vite-node] [plugin:nuxt:imports-transform] [VITE_ERROR] /@fs/Users/jeannen/Dev/apps/node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue?macro=true\n\n/* Injection by vite-plugin-vue-inspector Start */\nimport { createVNode as __createVNode } from 'vue'\nfunction _interopVNode(vnode) {\n if (vnode && vnode.props && 'data-v-inspector' in vnode.props) {\n const data = vnode.props['data-v-inspector']\n delete vnode.props['data-v-inspector']\n Object.defineProperty(vnode.props, '__v_inspector', { value: data, enumerable: false })\n }\n return vnode\n}\nfunction _createVNode(...args) { return _interopVNode(__createVNode(...args)) }\n/* Injection by vite-plugin-vue-inspector End */\nimport { defineComponent as _defineComponent } from \"vue\";\nimport { onUnmounted, onMounted, reactive } from \"vue\";\nimport { pascalCase } from \"scule\";\nimport { defineAsyncComponent, useColorMode, useRoute } from \"#imports\";\nconst _sfc_main = /* @__PURE__ */ _defineComponent({\n __name: \"DevtoolsRenderer\",\n setup(__props, { expose: __expose }) {\n __expose();\n const route = useRoute();\n const component = route.query?.example ? defineAsyncComponent(() => import(`./examples/${route.query.example}.vue`)) : route.params?.slug && defineAsyncComponent(() => import(`../../runtime/components/${pascalCase(route.params.slug)}.vue`));\n const state = reactive({});\n function onUpdateRenderer(event) {\n state.props = { ...event.data.props };\n state.slots = { ...event.data.slots };\n }\n const colorMode = useColorMode();\n function setColorMode(event) {\n colorMode.preference = event.isDark ? \"dark\" : \"light\";\n }\n onMounted(() => {\n (void 0).parent.addEventListener(\"nuxt-ui-devtools:update-renderer\", onUpdateRenderer);\n (void 0).parent.addEventListener(\"nuxt-ui-devtools:set-color-mode\", setColorMode);\n });\n onUnmounted(() => {\n (void 0).parent.removeEventListener(\"nuxt-ui-devtools:update-renderer\", onUpdateRenderer);\n (void 0).parent.removeEventListener(\"nuxt-ui-devtools:set-color-mode\", setColorMode);\n });\n onMounted(async () => {\n const event = new Event(\"nuxt-ui-devtools:component-loaded\");\n (void 0).parent.dispatchEvent(event);\n });\n onMounted(() => {\n if (!route.query?.example) return;\n });\n const __returned__ = { route, component, state, onUpdateRenderer, colorMode, setColorMode };\n Object.defineProperty(__returned__, \"__isScriptSetup\", { enumerable: false, value: true });\n return __returned__;\n }\n});\nimport { resolveComponent as _resolveComponent, resolveDynamicComponent as _resolveDynamicComponent, mergeProps as _mergeProps, withCtx as _withCtx, openBlock as _openBlock, createBlock as _createBlock, createCommentVNode as _createCommentVNode } from \"vue\";\nimport { ssrRenderVNode as _ssrRenderVNode, ssrRenderComponent as _ssrRenderComponent, ssrRenderAttrs as _ssrRenderAttrs } from \"vue/server-renderer\";\nfunction _sfc_ssrRender(_ctx, _push, _parent, _attrs, $props, $setup, $data, $options) {\n const _component_UApp = _resolveComponent(\"UApp\");\n _push(`\u003Cdiv${_ssrRenderAttrs(_mergeProps({\n id: \"ui-devtools-renderer\",\n class: \"nuxt-ui-component-renderer\",\n \"data-v-inspector\": \"../node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue:44:3\"\n }, _attrs))}>`);\n _push(_ssrRenderComponent(_component_UApp, { toaster: null }, {\n default: _withCtx((_, _push2, _parent2, _scopeId) => {\n if (_push2) {\n if ($setup.component) {\n _ssrRenderVNode(_push2, _createVNode(_resolveDynamicComponent($setup.component), _mergeProps($setup.state.props, {\n class: $setup.state?.slots?.base,\n ui: $setup.state.slots\n }), null), _parent2, _scopeId);\n } else {\n _push2(`\u003C!---->`);\n }\n } else {\n return [\n $setup.component ? (_openBlock(), _createBlock(_resolveDynamicComponent($setup.component), _mergeProps({ key: 0 }, $setup.state.props, {\n class: $setup.state?.slots?.base,\n ui: $setup.state.slots\n }), null, 16, [\"class\", \"ui\"])) : _createCommentVNode(\"v-if\", true)\n ];\n }\n }),\n _: 1\n /* STABLE */\n }, _parent));\n _push(`\u003C/div>`);\n}\nimport \"/Users/jeannen/Dev/apps/node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue?vue&type=style&index=0&lang.css\";\nimport { useSSRContext as __vite_useSSRContext } from \"vue\";\nconst _sfc_setup = _sfc_main.setup;\n_sfc_main.setup = (props, ctx) => {\n const ssrContext = __vite_useSSRContext();\n (ssrContext.modules || (ssrContext.modules = /* @__PURE__ */ new Set())).add(\"../../node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue\");\n return _sfc_setup ? _sfc_setup(props, ctx) : void 0;\n};\nimport _export_sfc from \"\\0plugin-vue:export-helper\";\nexport default /* @__PURE__ */ _export_sfc(_sfc_main, [[\"ssrRender\", _sfc_ssrRender], [\"__file\", \"/Users/jeannen/Dev/apps/node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue\"]]);\n\nat /@fs/Users/jeannen/Dev/apps/node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue?macro=true\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3209,3210,3213],{"name":3173,"color":3174},{"name":3211,"color":3212},"duplicate","cfd3d7",{"name":3176,"color":3177},2823,"`colorMode: false` + /pages/ crash the app","2024-12-03T09:33:17Z","https://github.com/nuxt/ui/issues/2823",0.7055598,{"description":3220,"labels":3221,"number":3228,"owner":3182,"repository":3183,"state":3201,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@10.6.1\n- Builder: -\n- User Config: ssr, dev, debug, app, modules, devtools, css, icon, future, nitro, vite, compatibilityDate, typescript, runtimeConfig, eslint\n- Runtime Modules: @nuxt/eslint@1.1.0, @nuxt/ui-pro@3.0.0-beta.2, @nuxt/image@1.9.0, @vueuse/nuxt@12.7.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-beta.2\n\n### Reproduction\n\nFor the PageList component, the first child is correctly converted to a li, the remaining ones are still divs and haven't been converted. Also, the data-orientation value of the first li is incorrectly forced to vertical.\n\n### Description\n\nFor the PageList component, the first child is correctly converted to a li, the remaining ones are still divs and haven't been converted. Also, the data-orientation value of the f\n\n\u003Cimg width=\"603\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1db776b9-a16f-4788-8834-c68dfa931c7f\" />\n\nirst li is incorrectly forced to vertical.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3222,3223,3224,3227],{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3225,"color":3226},"pro","5BD3CB",{"name":3179,"color":3180},3485,"For the PageList component, the first child is correctly converted to a li, the remaining ones are still divs and haven't been converted. Also, the data-orientation value of the first li is incorrectly forced to vertical.","2025-03-08T16:32:27Z","https://github.com/nuxt/ui/issues/3485",0.7081988,{"description":3234,"labels":3235,"number":3242,"owner":3182,"repository":3182,"state":3201,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v16.17.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: modules, colorMode, runtimeConfig\r\n- Runtime Modules: @tailwindcss/typography@0.5.9, @nuxtjs/tailwindcss@6.8.0, @pinia/nuxt@0.4.11, @nuxtjs/color-mode@3.3.0, nuxt-icon@0.4.2\r\n- Build Modules: -\r\n------------------------------\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/sandbox/keen-sea-66ccg7\r\n\r\n### Describe the bug\r\n\r\nWe have a useDimensions composable which returns the dimension of the window.\r\n\r\nWe also have a simple vue file:\r\n\r\n```\r\n \u003Cdiv>\r\n {{ dimensions.width }}\r\n \u003Cdiv v-if=\"dimensions.width > 1200\" class=\"red\">\r\n \u003Cspan>Who let the dogs out\u003C/span>\r\n \u003C/div>\r\n \u003Cdiv v-else class=\"green\">Wof Wof\u003C/div>\r\n \u003C/div>\r\n```\r\n\r\nwhich based on the useDimensions composable returns either DIV1 or DIV2.\r\n\r\n1. The webpage renders on server side using a default preset value (`390x900`) which will render DIV2 (in production this should only happen the first time you access the website).\r\n2. When the onmounted event happens we update the resolution using the actual resolution (let's say `1920x1080`).\r\n3. The content of the two divs update accordingly, however the classes on the div remain the same: https://ibb.co/ZWFxyHk\r\n\r\n\r\n\r\nThe update happens in the onmounted event, at first the website should have been rendered using the initial resolution 390x900 and then it should have been updated to the 1920x1080 dimensions.\r\n\r\n\r\n\r\n### Additional context\r\n\r\nAs a workaround we use CSS to render different elements on different dimensions, however sometimes it makes more sense to render some elements based on JS logic (like the number of elements of a carousel).\r\n\r\n`v-show` should fix this issue as both divs are printed and the updated, however in some cases you might not want to use it (you don't want to print 1000 elements).\r\n\r\n### Logs\r\n\r\n_No response_",[3236,3239],{"name":3237,"color":3238},"3.x","29bc7f",{"name":3240,"color":3241},"pending triage","E99695",22517,"Bad rendering when a variable value changes from server side rendering to client side rendering","2023-08-07T08:29:52Z","https://github.com/nuxt/nuxt/issues/22517",0.70923936,{"description":3248,"labels":3249,"number":3252,"owner":3182,"repository":3183,"state":3201,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/weathered-resonance-r7wcmc?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nThe carousel item generic type does not seem to work anymore. Unfortunately I'm not sure, which is the last version of nuxt ui where it works :(\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n'item' is possibly 'null'. \nProperty 'title' does not exist on type 'string | number | Record\u003Cstring, any>'.\n Property 'title' does not exist on type 'string'.\n```",[3250,3251],{"name":3173,"color":3174},{"name":3176,"color":3177},4020,"Generic Type Issue with Carousel Component","2025-04-29T15:39:36Z","https://github.com/nuxt/ui/issues/4020",0.7106725,{"description":3258,"labels":3259,"number":3266,"owner":3182,"repository":3183,"state":3201,"title":3267,"updated_at":3268,"url":3269,"score":3270},"### Environment\n\n- Nuxt Vesrion: '3.15.1'\n- Nuxt/ui Version: '3.0.1'\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.15.1\n\n### Reproduction\n\nhttps://github.com/nuxt/ui/pull/2251\n\n### Description\n\nThis issue was previously addressed and fixed in [PR #2251](https://github.com/nuxt/ui/pull/2251). However, after upgrading to Nuxt UI v3.0.1, the dir prop no longer exists, making it impossible to switch the direction of the Carousel.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3260,3261,3264,3265],{"name":3173,"color":3174},{"name":3262,"color":3263},"needs reproduction","CB47CF",{"name":3176,"color":3177},{"name":3196,"color":3197},3705,"Missing \"dir\" Prop in Carousel Component After Nuxt UI v3.0.1 Update","2025-05-31T02:09:01Z","https://github.com/nuxt/ui/issues/3705",0.71350473,{"description":3272,"labels":3273,"number":3277,"owner":3182,"repository":3183,"state":3201,"title":3278,"updated_at":3279,"url":3280,"score":3281},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.10.0\n- Builder: -\n- User Config: modules, devtools, supabase, runtimeConfig, security, css, uiPro, routeRules, future, compatibilityDate, nitro, content, eslint\n- Runtime Modules: @nuxt/eslint@1.4.1, @nuxt/image@1.10.0, @nuxt/ui-pro@3.1.3, @nuxt/content@3.6.0, @vueuse/nuxt@13.4.0, nuxt-og-image@5.1.7, @nuxtjs/supabase@1.5.2, nuxt-security@2.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\n## Steps to Reproduce:\n1. Load the StackBlitz demo: https://stackblitz.com/edit/nuxtui-carousel-fade-bug\n2. Click the tabs on the carousel - notice the smooth fade transitions ✅\n3. Navigate to \"Page 2\" using the button\n4. Try clicking tabs on either page - fade transitions no longer work ❌\n5. The carousel now uses slide animations instead of fade\n\n### Description\n\nI noticed that when using page transitions, the `fade` property of the `\u003CUCarousel>` component stops working after navigating between pages. The carousel reverts to slide animations instead of fade transitions. Removing the page transitions restores correct functionality.\n\nI looked into it with the help of Claude and found the bug was caused by VueUse's computedAsync failing during page transitions in Nuxt. I will open a PR to fix this issue!\n\n### Additional context\n\n## Expected Behavior:\nCarousel fade transitions should continue working after page navigation with transitions.\n\n## Actual Behavior:\nCarousel fade transitions stop working and revert to slide animations after navigating between pages that have `pageTransition` configured.\n\n## Workaround:\nRemoving `pageTransition` from `definePageMeta()` restores fade functionality even after navigation.\n\n\n### Logs\n\n```shell-script\n\n```",[3274,3275,3276],{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3179,"color":3180},4379,"UCarousel fade transitions break after page navigation with pageTransition","2025-06-30T12:55:09Z","https://github.com/nuxt/ui/issues/4379",0.7153213,{"description":3283,"labels":3284,"number":3288,"owner":3182,"repository":3183,"state":3201,"title":3289,"updated_at":3290,"url":3291,"score":3292},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\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`, `srcDir`, `routeRules`, `app`, `svgSprite`, `alias`, `css`, `imports`, `modules`, `ssr`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.14.0`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.8`, `@nuxt/test-utils@3.19.1`, `@nuxt/ui@3.1.3`, `@nuxtjs/svg-sprite@1.0.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dreamy-euler-9595k7\n\n\n### Description\n\n\n\nHi when i select copy payment id i got that error when i console log the row it gives me undefined upon clicking kindly check this link: https://ui.nuxt.com/components/table#with-context-menu\n\n#4259 \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3285,3286,3287],{"name":3173,"color":3174},{"name":3262,"color":3263},{"name":3176,"color":3177},4452,"UTable context menu error during selection of items","2025-07-13T16:34:46Z","https://github.com/nuxt/ui/issues/4452",0.71845025,{"description":3294,"labels":3295,"number":3300,"owner":3182,"repository":3182,"state":3201,"title":3301,"updated_at":3302,"url":3303,"score":3304},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `modules`, `sanity`, `googleFonts`, `sitemap`, `nitro`\r\n- Runtime Modules: `@nuxtjs/sanity@1.6.0`, `@nuxtjs/tailwindcss@6.4.1`, `@nuxtjs/google-fonts@3.0.0-1`, `nuxt-schema-org@2.1.2`, `nuxt-icon@0.1.8`, `@vueuse/nuxt@9.13.0`, `nuxt-headlessui@1.1.1`, `@morev/vue-transitions/nuxt@2.3.6`, `nuxt-simple-sitemap@1.0.9`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nSorry, but I couldn't get folder based page routing to work on StackBlitz and CodeSandbox is not working. (please provide some guidance if possible)\r\n\r\nInstead, you I wrote out the code to reproduce this below:\r\n\r\n## Directory Structure\r\n- app.vue\r\n- /pages\r\n - index.vue\r\n - about.vue\r\n- /layouts\r\n - default.vue\r\n \r\n## Code\r\n### app.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n\u003C/template>\r\n```\r\n### /pages/index.vue\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst route = useRoute();\r\nconsole.log(route.fullPath);\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>Home page\u003C/h1>\r\n \u003CNuxtLink to=\"/about\">About Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n### /pages/about.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>About page\u003C/h1>\r\n \u003CNuxtLink to=\"/\">Home Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n### /layouts/default.vue\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst route = useRoute();\r\nconsole.log(route.fullPath);\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cmain>\r\n \u003Cslot />\r\n \u003C/main>\r\n\u003C/template>\r\n```\r\n## Steps to reproduce\r\n1. Land on the home page\r\n2. View your console and note the logs produced by `/pages/index.vue` and `/layout/default.vue`\r\n3. Press the NuxtLink to go to the about page\r\n4. Press the NuxtLink on the about page to go back to the home page\r\n5. View your console and note the logs produced by `/pages/index.vue` and `/layout/default.vue`\r\n## Behavior\r\n**Current:**\r\n- When first landing on the home page, the logs of the page and the layout are consistent (both show '/' for the `fullPath`)\r\n- Upon navigating to the about page and return to the home page, the logs are different:\r\n - the page logs correctly: `/`\r\n - the layout logs incorrectly: `/about`\r\n\r\n**Expected:**\r\n- Both the layout and the page should have consistent logs (i.e. retrieve the same value from `useRoute()`)\r\n- The layout should display the correct `fullpath`, even when navigating away and returning using the NuxtLink (i.e. it should have logged '/' instead of '/about/' since we are on the home page)\r\n\r\n### Describe the bug\r\n\r\nWhen calling `useRoute()` inside of a layout, it will retrieve the correct value on the initial load or when refreshing the page. Once navigating away using a NuxtLink, it appears to retrieve an incorrect/old value (possibly due to client-side rendering). Please see the reproduction section for details.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3296,3297],{"name":3240,"color":3241},{"name":3298,"color":3299},"possible regression","B90A42",21340,"useRoute providing incorrect data when used in a layout","2025-06-18T21:11:10Z","https://github.com/nuxt/nuxt/issues/21340",0.72040606,["Reactive",3306],{},["Set"],["ShallowReactive",3309],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ft3AOU4c6WdJ2JDxpXjImBfjohSTZjZtZ4379CfU9n-Y":-1},"/nuxt/ui/1605"]