Zod custom error object parses incorrectly, using multiple paths","2025-04-14T17:17:53Z","https://github.com/nuxt/ui/issues/3894",0.70951855,{"description":3155,"labels":3156,"number":3163,"owner":3147,"repository":3147,"state":3164,"title":3165,"updated_at":3166,"url":3167,"score":3168},"### Environment\n\nclean setup on stackblitz\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\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-ketx95?file=app.vue\r\n\r\n1. Please open devtools, \r\n2. Click any product on the list \r\n3. Notice there is two console.logs 'render' with two different instances of the same component. Described results on the video below: \r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/1b308d97-255d-435d-9d5b-439a2d049c1a\r\n\r\n\n\n### Describe the bug\n\n## Context\r\nWe use:\r\n+ dynamic page - `[...slug].vue`\r\n+ dynamic components - `component :is`\r\n\r\nScenario\r\n1. Fetch pageData on `[...slug].vue` by `useAsyncData`\r\n2. Render dynamic components based on `pageData`\r\n\r\n## A bug / a question? \r\nPlease click on some links in the product list (under \"Reproduction\").\r\nThe question is, why are components being rendered twice? This is causing unexpected bugs.\r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/1b308d97-255d-435d-9d5b-439a2d049c1a\r\n\r\nWe could prevent the double rendering by adding a :key to NuxtPage, but this would cause the page components to rerender before asyncData is resolved, which could have some impact. In this example, when we add :key, the components are only rendered once, but the page component is empty and does not wait for asyncData to render.\r\n\r\nhttps://github.com/nuxt/nuxt/assets/7935392/f546fea4-3d03-41bb-b083-cc068a85bd50\r\n\r\nHow to prevent the effect of double rendering?\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3157,3160],{"name":3158,"color":3159},"3.x","29bc7f",{"name":3161,"color":3162},"pending triage","E99695",20848,"closed","Components are rendered twice (\u003Ccomponent :is> on [...slug].vue) ","2024-05-25T19:30:19Z","https://github.com/nuxt/nuxt/issues/20848",0.6777179,{"labels":3170,"number":3175,"owner":3147,"repository":3147,"state":3164,"title":3176,"updated_at":3177,"url":3178,"score":3179},[3171,3172],{"name":3161,"color":3162},{"name":3173,"color":3174},"2.x","d4c5f9",7324,"Nuxt-child rendered multiple times in nested route with component","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7324",0.6838532,{"description":3181,"labels":3182,"number":3188,"owner":3147,"repository":3147,"state":3164,"title":3189,"updated_at":3190,"url":3191,"score":3192},"### Environment\r\n\r\n```\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.4.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.7.2\r\n- Builder: -\r\n- User Config: devtools, css, modules, site, components, app\r\n- Runtime Modules: @nuxt/content@2.9.0, @vueuse/nuxt@10.7.0, nuxt-simple-sitemap@4.1.17, nuxt-jsonld@2.0.8\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-snapag?file=content%2Fblog%2Ftest.md\r\n\r\n### Describe the bug\r\n\r\nI am on nuxt `3.8.2` with no issues, since I ran `npx nuxi upgrade` my blog articles broke. I did some experimenting and I noticed that the content components are not working.\r\n\r\nFor example, this now breaks in `3.9.1` but works in the version I am running `3.8.2`.\r\n\r\nNOTE: this only happens if there is camel casing in the components content name, e.g. `FooBar.vue` breaks, `Foobar.vue` works.\r\n\r\n\u003Cpre>\r\n\u003C!-- Custom Component in the content directory - FooBar.vue -->\r\n::FooBar\r\nsome p text\r\n::\r\n\u003C/pre>\r\nThis will output in the html\r\n```html\r\n\u003Cfoobar>\r\n \u003Cp>some p text\u003C/p>\r\n\u003C/foobar>\r\n```\r\n\r\nIn the `FooBar.vue` component\r\n```html\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"foobar\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nSo the expected result is \r\n```html\r\n\u003Cdiv class=\"foobar\">\r\n \u003Cp>some p text\u003C/p>\r\n\u003C/div>\r\n```\r\n\r\nBut we get \r\n```html\r\n\u003Cfoobar>\r\n \u003Cp>some p text\u003C/p>\r\n\u003C/foobar>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3183,3184,3185],{"name":3158,"color":3159},{"name":3161,"color":3162},{"name":3186,"color":3187},"needs reproduction","FBCA04",25166,"Camel Cased Content Components Do Not Render in Nuxt 3.9.1","2024-01-12T13:47:20Z","https://github.com/nuxt/nuxt/issues/25166",0.6851379,{"description":3194,"labels":3195,"number":3198,"owner":3147,"repository":3147,"state":3164,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\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------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-hsectr-l7wusd?file=btn.vue,app.vue\r\n\r\n### Describe the bug\r\n\r\nWhen using nested functional `h` components and showing conditionally lowest level component, nuxt renders only once this component and then just stops render it. \r\nIn provided link please toggle click button `Show/hide functional component` at least 3 times to show -> hide -> show, to see issue.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3196,3197],{"name":3158,"color":3159},{"name":3161,"color":3162},20871,"Nested Functional Component render only once ","2023-07-27T15:48:22Z","https://github.com/nuxt/nuxt/issues/20871",0.6870344,{"labels":3204,"number":3209,"owner":3147,"repository":3147,"state":3164,"title":3210,"updated_at":3211,"url":3212,"score":3213},[3205,3207,3208],{"name":3206,"color":3145},"stale",{"name":3161,"color":3162},{"name":3173,"color":3174},10059,"Can't open more than 3 tabs","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10059",0.6997747,{"labels":3215,"number":3218,"owner":3147,"repository":3147,"state":3164,"title":3219,"updated_at":3220,"url":3221,"score":3222},[3216,3217],{"name":3161,"color":3162},{"name":3173,"color":3174},8281,"\u003Cclient-only> causing component to render twice","2023-01-22T15:38:17Z","https://github.com/nuxt/nuxt/issues/8281",0.7024274,{"labels":3224,"number":3227,"owner":3147,"repository":3147,"state":3164,"title":3228,"updated_at":3229,"url":3230,"score":3231},[3225,3226],{"name":3158,"color":3159},{"name":3161,"color":3162},13547,"Dynamic component with auto imported components (component is)","2023-01-19T16:59:16Z","https://github.com/nuxt/nuxt/issues/13547",0.7034514,{"description":3233,"labels":3234,"number":3238,"owner":3147,"repository":3147,"state":3164,"title":3239,"updated_at":3240,"url":3241,"score":3242},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.14.12\r\n- node: 14.15.0\r\n\r\n### Reproduction\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\n\r\n1. Create Vue.js component with a named slot of your choice\r\n2. Use created component and provide the content for the slot (wrap everything in `\u003Cclient-only>` tag); example below:\r\n```\r\n\u003CStepper\r\n :steps=\"[$t('steps.one'), $t('steps.two'), $t('steps.three')]\"\r\n>\r\n \u003Ctemplate slot=\"step-1\">\r\n \u003Cdiv>\r\n \u003Cclient-only placeholder=\"Loading...\">\r\n \u003C!-- Neither a span tag nor v-calendar plugin works (tested one by one) -->\r\n \u003Cspan>Test\u003C/span>\r\n \u003Cdiv>\r\n \u003Cv-date-picker\r\n v-model=\"dates\"\r\n is-expanded\r\n trim-weeks\r\n />\r\n \u003C/div>\r\n \u003C/client-only>\r\n \u003C/div>\r\n \u003C/template>\r\n\u003C/Stepper>\r\n```\r\nThe placeholder remains with no content replaced as shown below:\r\n\r\n\r\n### What is Expected?\r\nContent inside `\u003Cclient-only>` tag should get rendered instead of getting stuck on the placeholder (or blank state if placeholder not provided).\r\n\r\n### What is actually happening?\r\n`\u003Cclient-only>` tag does not render its content when the tag is placed inside a component slot, as shown in the provided example. It does render when placed outside of the slot.",[3235,3236,3237],{"name":3206,"color":3145},{"name":3161,"color":3162},{"name":3173,"color":3174},8579,"Client-only content doesn't render in component's slot","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8579",0.7053382,{"description":3244,"labels":3245,"number":3252,"owner":3147,"repository":3148,"state":3164,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.2\n- Nuxt Version: 3.13.0\n- CLI Version: 3.13.0\n- Nitro Version: 2.9.7\n- Package Manager: yarn@3.7.0\n- Builder: -\n- User Config: app, modules, algolia, content, fonts, colorMode, tailwindcss, site, schemaOrg, nitro, runtimeConfig, sourcemap, experimental, compatibilityDate\n- Runtime Modules: @nuxt/content@2.13.2, @nuxt/image@1.7.0, @nuxt/ui@2.18.4, @nuxt/fonts@0.6.1, nuxt-og-image@3.0.0-rc.65, @nuxtjs/algolia@1.10.2, nuxt-schema-org@2.2.0\n- Build Modules: -\n------------------------------\n\n### Version\n\nv2.18.3\n\n### Reproduction\n\n1. Go to https://ui.nuxt.com/components/tabs?tab=Tab1#control-the-selected-index\n\n2. Click on any tab that is not tab 1 (`tabs?tab=Tab3#control-the-selected-index`)\n\n3. Copy the link to that tab and paste it in a new browser tab or reload page\n4. The tab is not rendered correctly\n\n\n\n\n### Description\n\nLinks to the tabs don't work correctly, they don't render at all\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3246,3247,3248,3251],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3249,"color":3250},"closed-by-bot","ededed",{"name":3206,"color":3250},2356,"[Tabs] Tabs don't render correctly, even on the documentation page","2025-06-18T09:05:59Z","https://github.com/nuxt/ui/issues/2356",0.7073848,["Reactive",3258],{},["Set"],["ShallowReactive",3261],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6sf3xMIubg7Ea_wleMeJ7hWvPkhv0LCWdju81YDob6s":-1},"/nuxt/ui/2044"]