\n {{ selectedTheme }}\n \u003Cbr />\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\n defineProps({\n media: {\n type: Object,\n required: true,\n },\n });\n\n const mediaPresets = useMediaPresets();\n\n const selectedTheme = ref('');\n\n const themeOptions = computed(() => {\n return mediaPresets.themes.map((theme) => ({\n id: theme.id,\n label: `${theme.emoji} ${theme.display}`,\n }));\n });\n\u003C/script>\n\n```\n\n\nWorking / Fix:\n```Vue\n\u003Ctemplate>\n \u003CUSelectMenu v-model=\"themesProxy\" name=\"labels\" :options=\"themeOptions\" searchable creatable placeholder=\"Select labels\" />\n {{ selectedTheme }}\n \u003Cbr />\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\n defineProps({\n media: {\n type: Object,\n required: true,\n },\n });\n const mediaPresets = useMediaPresets();\n\n const selectedTheme = ref('my_value');\n\n const themeOptions = computed(() => {\n return mediaPresets.themes.map((theme) => ({ id: theme.id, label: `${theme.emoji} ${theme.display}` }));\n });\n\n const themesProxy = computed({\n get: () => {\n const existingTheme = themeOptions.value.find((theme) => theme.id === selectedTheme.value);\n if (existingTheme) return existingTheme;\n return { id: selectedTheme.value, label: selectedTheme.value?.replace(/\\s/g, '-')?.toLowerCase() };\n },\n\n set: (newValue: any) => {\n if (newValue.label && !newValue.id) newValue.id = newValue.label.replace(/\\s/g, '-').toLowerCase();\n selectedTheme.value = newValue.id;\n },\n });\n\n\u003C/script>\n\n```\n\n### Description\n\n\n\nWhen using the `creatable` option, the selected value does not show up properly in the input.\n\n\nThe v-model properly changes (`{{ selectedTheme }}` under the input), but it doesn't show up in the input afterward not in the \"create xyz' text \n\nThe issue seems to happens when not using `multiple`\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2034],{"name":2019,"color":2020},2342,"closed","[SelectMenu] `creatable` bugged when not using `multiple`","2024-11-12T17:11:21Z","https://github.com/nuxt/ui/issues/2342",0.7391848,{"description":2042,"labels":2043,"number":2048,"owner":1994,"repository":1994,"state":2036,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Describe the feature\r\n\r\nI hope this works in SSR mode.\r\ncurrently I have to wrap it in `\u003Cclient-only>`.\r\n\r\n```vue\r\n\u003Cteleport to=\"#test\">\r\n \u003Cdiv>test\u003C/div>\r\n\u003C/teleport>\r\n```\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2044,2047],{"name":2045,"color":2046},"3.x","29bc7f",{"name":2005,"color":2006},21597,"teleport to specific element ","2023-06-20T09:46:04Z","https://github.com/nuxt/nuxt/issues/21597",0.7404327,{"description":2054,"labels":2055,"number":2058,"owner":1994,"repository":1994,"state":2036,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.1\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-mdx82e?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nWhen using `Teleport` during SSR, the content is teleported **above** the main nuxt application. When using `Teleport` on the client-side, the content is teleported below. This causes issues with teleported modals / dropdowns etc.\r\n\r\n```html\r\n\u003CTeleport to=\"body\">\r\n \u003Cdiv>SSR teleport\u003C/div>\r\n\u003C/Teleport>\r\n\u003CClientOnly>\r\n \u003CTeleport to=\"body\">\r\n \u003Cdiv>Client teleport\u003C/div>\r\n \u003C/Teleport>\r\n\u003C/ClientOnly>\r\n```\r\n\r\nThe resulting HTML will look like this:\r\n```html\r\n\u003Cbody>\r\n \u003Cdiv>SSR teleport\u003C/div>\r\n \u003Cdiv id=\"__nuxt\">...\u003C/div>\r\n \u003Cdiv>Client teleport\u003C/div>\r\n\u003C/body>\r\n```\r\n\r\nI would have expected this result:\r\n```html\r\n\u003Cbody>\r\n \u003Cdiv id=\"__nuxt\">...\u003C/div>\r\n \u003Cdiv>SSR teleport\u003C/div>\r\n \u003Cdiv>Client teleport\u003C/div>\r\n\u003C/body>\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_",[2056,2057],{"name":2045,"color":2046},{"name":2005,"color":2006},24207,"Teleport behaves differently for SSR and client-side","2024-03-11T14:33:50Z","https://github.com/nuxt/nuxt/issues/24207",0.74070054,{"description":2064,"labels":2065,"number":2066,"owner":1994,"repository":2067,"state":2036,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### 📚 Description\r\n\r\nI got a 404 error when I accessed the **learn more** link on the [cloudflare](https://nuxt.com/deploy/cloudflare) page.\r\nI investigated the cause and found that the URL path was incorrect.",[],1520,"nuxt.com","bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.74695283,{"description":2073,"labels":2074,"number":2076,"owner":1994,"repository":1995,"state":2036,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[2075],{"name":1985,"color":1986},2398,"Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.7495041,{"description":2082,"labels":2083,"number":2090,"owner":1994,"repository":1994,"state":2036,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Describe the feature\r\n\r\nRight now we prepend SSR teleports to the body. This doesn't align with Vue's appending behavior. To give an alternative and also [align with Evan's recommendation](https://github.com/vuejs/core/issues/5242#issuecomment-1129829701), it would make sense to introduce a `#nuxt-teleports` div as possible target for SSR teleports.\r\n\r\nAdditional context: https://github.com/nuxt/nuxt/issues/24207\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2084,2086,2087],{"name":1985,"color":2085},"8DEF37",{"name":2045,"color":2046},{"name":2088,"color":2089},"🍰 p2-nice-to-have","0E8A16",25041,"Add support for SSR teleports to a separate `#nuxt-teleports` element ","2024-03-11T14:33:51Z","https://github.com/nuxt/nuxt/issues/25041",0.7515834,{"description":2096,"labels":2097,"number":2100,"owner":1994,"repository":2101,"state":2036,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.13.2\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-fvrlkg?file=tests/app.test.ts,app.vue\r\n\r\ncancel the running process in the terminal and run `npm test` - you will see the failure.\n\n### Describe the bug\n\nIt seems that when `registerEndpoint` is called on a path containing two levels deep such as `/api/foo`, then subsequent calls to registerEndpoint on paths containing that root will fail to register. Ie, `registerEndpoint('/api/foo/bar', ...)` will silently fail. Calls to that deeper path when run in the test context receive the shorter path's response.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2098],{"name":2005,"color":2099},"5D08F5",956,"test-utils","registerEndpoint fails to register on deep paths","2024-11-26T16:14:09Z","https://github.com/nuxt/test-utils/issues/956",0.7530123,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"8gjq297NPV_60Fmm3zowL_rhaAnns_H_Li0frR4mtIQ":-1},"/nuxt/ui/2287"]