Zod custom error object parses incorrectly, using multiple paths","2025-04-14T17:17:53Z","https://github.com/nuxt/ui/issues/3894",0.7046282,{"description":2920,"labels":2921,"number":2931,"owner":2912,"repository":2912,"state":2932,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Environment\n\nNuxt project info: 12:11:19\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ouse6d?file=app.vue\r\n\r\n\n\n### Describe the bug\n\nThe page should not show any content at all. But it does when the SSR rendered HTML is shown. And then turns black after hydration completes.\r\n\r\n\n\n### Additional context\n\nThis only happens when v-show is used on a Vue component that is a direct child of NuxtClientFallback.\n\n### Logs\n\n_No response_",[2922,2925,2928],{"name":2923,"color":2924},"3.x","29bc7f",{"name":2926,"color":2927},"pending triage","E99695",{"name":2929,"color":2930},"upstream","E8A36D",24650,"closed","v-show breaks when used in a Vue component that is a direct slot of NuxtClientFallback","2023-12-09T06:58:54Z","https://github.com/nuxt/nuxt/issues/24650",0.666544,{"description":2938,"labels":2939,"number":2945,"owner":2912,"repository":2912,"state":2932,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-zpzmng-lfbt8x?file=app.vue\n\n### Describe the bug\n\nMarking a component as client only using `xx.client.vue` stops v-show from working and instead displays the component all the time. v-if works fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2940,2941,2942],{"name":2923,"color":2924},{"name":2903,"color":2904},{"name":2943,"color":2944},"🔨 p3-minor","FBCA04",15014,"client only components don't respect v-show","2023-01-19T17:43:32Z","https://github.com/nuxt/nuxt/issues/15014",0.6741617,{"labels":2951,"number":2954,"owner":2912,"repository":2912,"state":2932,"title":2955,"updated_at":2956,"url":2957,"score":2958},[2952,2953],{"name":2923,"color":2924},{"name":2926,"color":2927},13444,"Dynamic components with component is","2023-01-19T16:56:14Z","https://github.com/nuxt/nuxt/issues/13444",0.67998564,{"description":2960,"labels":2961,"number":2965,"owner":2912,"repository":2913,"state":2932,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\n- Nuxt: 3.16.0.\n- Vue: 3.5.13.\n- Node: 18.\n- Nuxt UI: 3.0.0.\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nNA\n\n### Description\n\nHi. I created a new Nuxt project. Im working with the Nuxt UI v 3.0.0.\nI read the docs but I have problem with toast because is not showing when its being call.\n\nThis is my App.vue\n\n\u003Ctemplate>\n \u003CUApp>\n \u003CNuxtPage />\n \u003C/UApp>\n\u003C/template>\n\nindex.vue\n\n\u003Cscript setup lang=\"ts\">\nconst toast = useToast();\n\nfunction showToast() {\n toast.add({\n title: \"Title\",\n });\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUButton\n label=\"Show toast\"\n color=\"neutral\"\n variant=\"outline\"\n @click=\"showToast\"\n />\n\u003C/template>\n\n\nAnd this is my nuxt.config.ts\n\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n hooks: {\n \"prerender:routes\"({ routes }) {\n routes.clear();\n },\n },\n future: {\n compatibilityVersion: 4,\n },\n compatibilityDate: \"2024-11-01\",\n devtools: { enabled: true },\n modules: [\"@nuxt/ui\", \"@vueuse/nuxt\", \"@nuxt/eslint\"],\n css: [\"~/assets/css/main.css\"],\n ui: {\n fonts: false,\n //colorMode: false,\n theme: {},\n },\n ssr: false,\n router: {\n options: {\n hashMode: true,\n },\n },\n eslint: {\n config: {\n stylistic: true,\n },\n },\n});\n\nI tried working with a nuxt.config.ts by default settings but it didnt work neither.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2962,2963,2964],{"name":2903,"color":2904},{"name":2906,"color":2907},{"name":2909,"color":2910},3564,"Toast not showing","2025-03-18T19:06:18Z","https://github.com/nuxt/ui/issues/3564",0.6856208,{"labels":2971,"number":2978,"owner":2912,"repository":2912,"state":2932,"title":2979,"updated_at":2980,"url":2981,"score":2982},[2972,2974,2975],{"name":2973,"color":2910},"stale",{"name":2926,"color":2927},{"name":2976,"color":2977},"2.x","d4c5f9",10129,"SSR doesn't render `v-else` component after component with `v-html`","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10129",0.6882043,{"labels":2984,"number":2989,"owner":2912,"repository":2912,"state":2932,"title":2990,"updated_at":2991,"url":2992,"score":2993},[2985,2986,2987],{"name":2923,"color":2924},{"name":2926,"color":2927},{"name":2988,"color":2944},"needs reproduction",14031,"Support for vue devtools","2023-01-19T17:27:46Z","https://github.com/nuxt/nuxt/issues/14031",0.69019866,{"description":2995,"labels":2996,"number":3001,"owner":2912,"repository":2912,"state":2932,"title":3002,"updated_at":3003,"url":3004,"score":3005},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: yarn@4.4.1\r\n- Builder: -\r\n- User Config: future, srcDir, dir, components, alias, typescript, devtools, modules, routeRules, tailwindcss, postcss, compatibilityDate\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.1, @nuxt/image@1.8.0, @nuxt/eslint@0.5.5, @nuxt/content@2.13.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nNot working hover events demo: nuxt@3.13.1 + vue@3.5.2\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-squnun?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking demo: nuxt@3.13.0 + vue@3.4.8\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-uiqqjl?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking non-nuxt demo: Vite(vike) + vue@3.5.2\r\nhttps://stackblitz.com/edit/dajced?file=pages%2Findex%2F%2BPage.vue,components%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\n\n### Describe the bug\n\n- Open non-working demo\r\n- Wait for the server to start up\r\n- Reload the page (1/twice)\r\n- Hover over the thumbs.\r\n- Navigation should work, but nothing happens, although the carousel itself is initialized\r\n\r\nIn working demos all works fine.\n\n### Additional context\n\nI don't understand what must have been changed in nuxt for my code to stop working.\r\nCan you look at the source code of the `useThumbCarousel` hook that links carousel initialization with expected behavior - maybe there is some part of the code there that causes problems? I'm thinking about watchers or refs.\n\n### Logs\n\n_No response_",[2997,2998],{"name":2926,"color":2927},{"name":2999,"color":3000},"possible regression","B90A42",28856,"Something broken with latest vue (3.5.2+) and latest nuxt (3.13.1)","2024-09-11T19:49:43Z","https://github.com/nuxt/nuxt/issues/28856",0.6913758,{"description":3007,"labels":3008,"number":3011,"owner":2912,"repository":2912,"state":2932,"title":3012,"updated_at":3013,"url":3014,"score":3015},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, vite\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-s3ebia?file=app.vue,components%2FFullscreenBackground.vue\r\n\r\n### Describe the bug\r\n\r\nI was making a background for a modal component when I noticed a strange behaviour with the `\u003CTransition />` component, specifically when the `appear` prop is set.\r\n\r\nIt seems that the click event listener on an element inside `\u003CTransition appear>` isn't being properly handled.\r\nSteps to reproduce:\r\n1. open the reproduction\r\n2. click on the semi-transparent fullscreen div\r\n3. *nothing happens* even though it should have set its visibility to `false`\r\n\r\n1. remove `appear` from the `\u003CTransition>` component in `FullscreenBackground.vue`\r\n2. repeat the same steps & now the click is properly handled\r\n\r\n### Additional context\r\n\r\nI've tried and I couldn't reproduce the same issue in Vue, so I assume it could be a bug in Nuxt.\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3009,3010],{"name":2923,"color":2924},{"name":2926,"color":2927},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.6933514,{"description":3017,"labels":3018,"number":3020,"owner":2912,"repository":2912,"state":2932,"title":3021,"updated_at":3022,"url":3023,"score":3024},"### Environment\n\nNuxt project info: \n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\n[Playground with toogle not showing the second input on click ](https://stackblitz.com/edit/github-fcvwur?file=app.vue)\n\n### Describe the bug\n\nWith `npm run dev`, using `v-show` on an component with `defineOptions({ inheritAttrs: false });` and `v-bind=\"$attrs\"` is resulting in `display:none;` applied on the root div of the subcomponent (good behavior)+ the binded `$attrs` div if the initial `v-show` value is `false` (not good behavior).\n\nConsidering the following tree of components:\n```html\n\u003Cscript setup>const display = ref(false);\u003C/script>\n\u003Cdiv>\n \u003Cdiv v-show=\"!display\">\n \u003Cdiv>Normal component OK\u003C/div>\n \u003C/div>\n \u003Cdiv v-show=\"display\"> \u003C!--- Here is display:none --->\n \u003Cdiv>\n \u003Cdiv v-bind=\"$attrs\">\u003C/div> \u003C!--- Here the display: none of v-show is set as well but should stay on the root level --->\n \u003C/div>\n \u003C/div>\n\u003C/div>\n```` \nEven with using keys, if we put the sub component `v-show` prop at `false`:\n\nInside the component:\n\nThe `label ` shows up but not the input with `v-bind=\"$attrs\"`:\n\nAs you can see the `display:none;` prop was set to the input as well on first load but not removed when the toggle box was checked:\n\nAfter checked:\n\n\n\nI think the issue could be linked with: \n1. On SSR, Nuxt estimate that the `v-show` add the `display: none; ` style and figures out that the input has a `v-bind=\"$attrs\"` attribute, so it clone the style attribute and add it to the input html element as well.\n2. On Client side, the Vue app doesn't understand that the `display: none; ` is related to the same `v-show` condition than the root div, and fail to toogle it on checked.\n\n\n### Additional context\n\n There is no issues using only Vue in their playground: \n- [Example in vue official playground](https://play.vuejs.org/#eNrVVk1v2zgQ/StcYQFngdDuJu1htW6A7iKH7kdb7AbtISoKWRrZbGlSICnZhuH/3iEpSrSjJE1vvdjSvJnhm+E8UvvkVV1P2waSNJnrQrHaEA2mqclVJti6lsqQvYLqQCol1yRL0DVLfu+x16JuzAdmVq+MUWzRGNDBczobAe1So/HvlKzHQp19NOpGyiWHkxBv7P0zUUihDSlWUHyBkrwkWMtZlXMNvyDsQQNb81ZAB04mx8jNRh4h85lvE/ZnbmBd89wAPhMyL1lLCp5r/TJLavo8S5wZgZguzxfA0eENbAgIo3ZZQlq6lqWzdjzRNgvBcdaKw5bYH1pI3ucPK/TtCmZCvsAOw/6GHdaXJYO9pXolNwj91K8Yg4FO15kYDPz/sf9pjGAnClhJXoJC3DEiMg4OJcV8h8kYIY2tHyX9KOeTwKdxNnFwvw0z3Ae/zd3TfBbtfnKeGI0zU7Hl9LOWAtW0t87IVa5rxkG9rQ3DmcqSlDjEYjnncvOXsxnVwHmwu/pG7J/11tqy5J0CDarF3vaYydUSjIev/3+DTYhA7E3D0fsB8D/QkjeWo3f7oxEl0o78HNvXToBMLG/09daA0KEoS9R6Hpy/Oyf+fKD0ge7l9LmLy8QBu3gi4tNTCVvtldnmvLGKLaFiAv61e39m1enfnQrObidu4ycfB+B6zYwFmrrEjUvdzLy3qbxTpO0H1e10yBDXtEARgyLL/EjxbuGr/d6PHjkc5jNvivE+nQJchrVAmOBIkt6TnhSN0lLRWjJrjPXP/OTuagjyWEiclUgWrmFoCWtqRaXgO1KDzRRrEwsdBBLcN/Q3sqIvyGJJNyukRhZSoWi6P7rA5PTy2TOXjlayaHQqG+OqEXgIxHaF00Mv7lj6FEri6EFJq4Zz5+VdO9GneYW1p0blQtvNodvB8cRnlNuJSyjHv+Js4UwbejuZfOxM+cLpIngYWdPbi3obYA4VukcGzNgveERjqfLdHWv3clSyN61wv/3Tpn9yRTMrJopiPK4nWnc4va6GY8seXMMI3neI3XNj3/k44LlY2rMWRY2Bj4iu0//ZHud7BYoZm1ynxF3D5GAdH5P1k4QZLkinmotvF6UXUUjlN2hUQy1dMFGi4efcVtLL59Gu9h8z39HQczKJbivf3x+paWnE/skd/NSCslcN9u1y+mL662Vy+ArqKJrw)\n- [Example vue + vite playground](https://stackblitz.com/edit/vitejs-vite-5yi8n7?file=src%2FApp.vue)\n\n**Note:** after build with Nitro, the issue disappears.\n\n### Logs\n\n```shell-script\n-\n```",[3019],{"name":2926,"color":2927},30156,"SSR bug with v-show + inheritAttrs: false + v-bind=\"$attrs\"","2024-12-05T16:26:43Z","https://github.com/nuxt/nuxt/issues/30156",0.6992533,["Reactive",3026],{},["Set"],["ShallowReactive",3029],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3aJFbD4nKUfkho3xlcI0QKmPzXJmzhp0btRaYcwxWww":-1},"/nuxt/ui/4347"]