\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.",[1984,1987,1990],{"name":1985,"color":1986},"stale","ffffff",{"name":1988,"color":1989},"pending triage","E99695",{"name":1991,"color":1992},"2.x","d4c5f9",8579,"nuxt","closed","Client-only content doesn't render in component's slot","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8579",0.71445584,{"description":2001,"labels":2002,"number":2006,"owner":1994,"repository":2007,"state":1995,"title":2008,"updated_at":2009,"url":2010,"score":2011},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_02_25_at_17_19_52_5b7648bd53.mp4\n",[2003],{"name":2004,"color":2005},"bug","ff281a",90,"nuxt.com","(UI) USelect: placeholder put in the value","2023-02-15T12:30:37Z","https://github.com/nuxt/nuxt.com/issues/90",0.73482376,{"description":2013,"labels":2014,"number":2016,"owner":1994,"repository":2007,"state":1995,"title":2017,"updated_at":2018,"url":2019,"score":2020},"",[2015],{"name":2004,"color":2005},164,"`USelect` default value is not displayed after ssr load","2023-02-15T12:31:49Z","https://github.com/nuxt/nuxt.com/issues/164",0.7405279,{"labels":2022,"number":2025,"owner":1994,"repository":1994,"state":1995,"title":2026,"updated_at":2027,"url":2028,"score":2029},[2023,2024],{"name":1988,"color":1989},{"name":1991,"color":1992},9797,"after call error method in fetch navigation not working","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9797",0.74327856,{"description":2031,"labels":2032,"number":2034,"owner":1994,"repository":1994,"state":1995,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[2033],{"name":1988,"color":1989},28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.746715,{"description":2013,"labels":2040,"number":81,"owner":1994,"repository":2007,"state":1995,"title":2041,"updated_at":2042,"url":2043,"score":2044},[],"Profile dropdown","2023-02-15T12:30:30Z","https://github.com/nuxt/nuxt.com/issues/2",0.75078136,{"description":2013,"labels":2046,"number":679,"owner":1994,"repository":2007,"state":1995,"title":2047,"updated_at":2048,"url":2049,"score":2050},[],"Teams dropdown","2022-02-03T15:03:43Z","https://github.com/nuxt/nuxt.com/issues/1",0.7509102,{"description":2052,"labels":2053,"number":2058,"owner":1994,"repository":1994,"state":1995,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.11.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-boqtvs?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nWhen navigating between pages, the child page component is rendered two times and the first time with null property values and the second time with the actual value.\r\nAt the moment the only workaround is to check in the setup routine if the prop is defined and return an empty hyperscript block.\r\nBesides adding additional checks in the template, the typings for template vars are not present anymore.\r\n\r\n**Workaround**\r\n```typescript\r\n// ...\r\nsetup(props) {\r\n // todo: remove this when this is fixed in vue/nuxt\r\n if (!props.entity) {\r\n return () => h('div', []);\r\n }\r\n\r\n console.log(props.entity.attribute); // attempt to access property of undefined without previous check :/\r\n\r\n // ......\r\n},\r\n// ....\r\n```\r\n\r\n### Additional context\r\n\r\nhttps://github.com/nuxt/nuxt/issues/15035\r\n### Logs\r\n\r\n_No response_",[2054,2057],{"name":2055,"color":2056},"3.x","29bc7f",{"name":1988,"color":1989},20309,"Child Page- 2 times rendered (Properties: undefined than actual value)","2023-04-16T16:21:03Z","https://github.com/nuxt/nuxt/issues/20309",0.75314295,{"description":2064,"labels":2065,"number":2073,"owner":1994,"repository":1994,"state":1995,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Environment\n\nNuxt project info: 10:52:59 AM\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.15.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.9.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-d9qil3\n\nBe sure to open in full page, and open the dev console\n\n### Describe the bug\n\n`\u003CSomeComponent>.server.vue` actually still works, but if it contains a **selectiveClient** / `nuxt-client` element, this part is now broken, until you refresh or navigate to another page, using links and not the browser buttons (well refresh does work)\n\nWhether or not the server component contains a **selectiveClient** is irrelevant to the error message in the console, it will still throw that error\n\nHowever if it does contain a **selectiveClient**, then that part of the server component, is now broken\n\n### Additional context\n\nWhen using normal links (either a href, or \u003CNuxtLink>) this does not happen\n\nIt only happens when hitting the back button in the browser (or shortcut on mouse)\n\nEDIT:\nActually it does happen with NuxtLink's, the href is simply reloading the whole page, that's why it's not happening there\n\n### Logs\n\nruntime-core.esm-bundler.js?v=c0e84aa4:50 [Vue warn]: Failed to locate Teleport target with selector \"div[data-island-uid='1'][data-island-component=\"CounterButton-hb1RAsRv3M\"]\". Note the target element must exist before the component is mounted - i.e. the target cannot be rendered by the component itself, and ideally should be outside of the entire Vue component tree. \n at \u003CNuxtIsland name=\"HelloIsland\" > \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C Proxy(Object) {__v_skip: true} > > \n at \u003CAnonymous key=\"/\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/', path: '/', query: {…}, hash: '', name: 'index', …} ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CSideMenu ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CLayoutLoader key=\"side-menu\" layoutProps= {ref: RefImpl} name=\"side-menu\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"side-menu\" name=\"side-menu\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>",[2066,2067,2070],{"name":1988,"color":1989},{"name":2068,"color":2069},"needs reproduction","FBCA04",{"name":2071,"color":2072},"server components","839413",29345,"NuxtIsland: Failed to locate Teleport target with selector","2024-12-09T10:35:39Z","https://github.com/nuxt/nuxt/issues/29345",0.75616527,{"description":2079,"labels":2080,"number":2084,"owner":1994,"repository":1994,"state":1995,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.10.1`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.21`\r\n- Builder: `-`\r\n- User Config: `devtools`, `app`, `experimental`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\nflags:\r\n`{ experimental: { componentIslands: { selectiveClient: true } }`\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/marccremer/nuxt_islands_issue\n\n### Describe the bug\n\nWhen you rerender a server component it doesnt work on the inner client components.\r\nIn the example you change the props by clicking on the button.\r\nYou expect \"heyfalse\" to turn into \"heytrue\".\r\nNothing happens\n\n### Additional context\n\nThe given example works when you remove the baseUrl.\r\nIt seems that on rererend er the dynmic import doesnt take the baseUrl.\r\nIt should be `import(\"http://localhost:3000\"+baseUrl+\"component.vue\")`\r\nBut it does instead this\r\n`import(\"http://localhost:3000\"+\"component.vue\")`\r\nAnd doesnt find the import.\r\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: Failed to fetch dynamically imported module: http://localhost:3000/_nuxt/@fs/home/redacted/nuxt_island_issue/components/ClientShow.vue?import\n```\n",[2081,2082,2083],{"name":2055,"color":2056},{"name":1988,"color":1989},{"name":2071,"color":2072},25676,"Client component within server component not working, when app.baseUrl is set","2024-03-15T16:16:42Z","https://github.com/nuxt/nuxt/issues/25676",0.75621885,["Reactive",2090],{},["Set"],["ShallowReactive",2093],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"0fwIcX7ptQdWSGyTWALZEfI7-XQb3wBQNGegzfgAoSg":-1},"/nuxt/nuxt.com/220"]