\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_",[3043],{"name":3044,"color":3045},"bug","d73a4a",2342,"ui","closed","[SelectMenu] `creatable` bugged when not using `multiple`","2024-11-12T17:11:21Z","https://github.com/nuxt/ui/issues/2342",0.70501393,{"description":3054,"labels":3055,"number":3056,"owner":3021,"repository":3057,"state":3048,"title":3058,"updated_at":3059,"url":3060,"score":3061},"Hello everyone,\r\n\r\nI have a few questions about Nuxt test-utils.\r\n\r\nMy situation:\r\n\r\n- I have a Vue.js project with Vue test-utils;\r\n- I have a Nuxt.js project where I would like to add testing;\r\n\r\nI'm looking into different options for libraries to test my Nuxt.js project. Ideally, I would like to have something very similar to Vue test-utils, in order to avoid headaches when working on both projects. Nuxt test-utils seems like an interesting option, but I was wondering what are its advantages compared to just using Vue test-utils? Thanks!",[],451,"test-utils","Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/451",0.71480924,{"description":3063,"labels":3064,"number":3065,"owner":3021,"repository":3066,"state":3048,"title":3067,"updated_at":3068,"url":3069,"score":3070},"I think @Nuxt/fonts unable to download font meta data behind proxy server. All other tools (npm, pnpm) work fine.\r\n\r\n\r\nError:\r\n```bash\r\n[@nuxt/fonts] ERROR Could not download google font metadata. @nuxt/fonts will not be able to inject @font-face rules for google.\r\n\r\n\r\n[@nuxt/fonts] ERROR Could not download bunny font metadata. @nuxt/fonts will not be able to inject @font-face rules for bunny.\r\n\r\n\r\n[@nuxt/fonts] ERROR Could not download fontshare font metadata. @nuxt/fonts will not be able to inject @font-face rules for fontshare.\r\n```\r\n\r\nSystem info: \r\n```bash\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v21.6.2\r\n- Nuxt Version: 3.11.1\r\n- CLI Version: 3.11.0\r\n- Nitro Version: 2.9.4\r\n- Package Manager: pnpm@8.15.5\r\n- Builder: -\r\n- User Config: build, content, css, devtools, experimental, fonts, image, imports, lodash, modules, nitro, notivue, pinia, postcss, router, routeRules, runtimeConfig, security, seo, ssr, studio, telemetry, typescript, vite, vuetify, vueuse, vue\r\n- Runtime Modules: @nuxt/content@2.12.1, @nuxt/fonts@0.3.0, @nuxt/image@1.4.0, @nuxt/test-utils/module@3.12.0, @nuxthq/studio@1.0.13, @nuxtjs/seo@2.0.0-rc.9, @pinia/nuxt@0.5.1, @sidebase/nuxt-pdf@1.0.0-alpha.0, @vue-email/nuxt@0.8.19, @vueuse/nuxt@10.9.0, notivue/nuxt, nuxt-auth-utils@0.0.20, nuxt-lodash@2.5.3, nuxt-security@1.2.2, vuetify-nuxt-module@0.12.0\r\n- Build Modules: -\r\n------------------------------\r\n```",[],76,"fonts","ERROR: Could not download font metadata","2024-03-20T14:30:12Z","https://github.com/nuxt/fonts/issues/76",0.7205681,{"description":3072,"labels":3073,"number":3074,"owner":3021,"repository":3035,"state":3048,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### 📚 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,"bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.72113836,{"description":3080,"labels":3081,"number":3087,"owner":3021,"repository":3035,"state":3048,"title":3088,"updated_at":3089,"url":3090,"score":3091},"I cannot close an event on mobile, cannot click on the background and where is the close button?\n\nhttps://user-images.githubusercontent.com/904724/180490491-67f8af29-2262-4a85-a008-9b14d11fed7b.MOV",[3082,3084],{"name":3044,"color":3083},"ff281a",{"name":3085,"color":3086},"responsive","1cd1c6",817,"[Resources] Live events responsive issues","2023-02-15T12:31:00Z","https://github.com/nuxt/nuxt.com/issues/817",0.72919625,{"description":3093,"labels":3094,"number":3098,"owner":3021,"repository":3057,"state":3048,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### 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_",[3095],{"name":3096,"color":3097},"pending triage","5D08F5",956,"registerEndpoint fails to register on deep paths","2024-11-26T16:14:09Z","https://github.com/nuxt/test-utils/issues/956",0.7401943,{"description":3104,"labels":3105,"number":3112,"owner":3021,"repository":3047,"state":3048,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Description\n\nI'm building a UI with Slideover that lets users inspect table rows by clicking on them, and the inspector detail is inside a Slideover. Clicking a row opens a Slideover by setting its `v-model:open` to `true`. With `:overlay=\"false\"` and `:modal=\"false\"` so users can see and interact with content outside the Slideover, clicking on a second row changes the Slideover's content to be the inspector for that second row (so they can inspect a different row with only a single click). However, the Slideover correctly detects the click outside of the Slideover and closes briefly, only to immediately reopen because the click was on another row to be inspected (which sets `v-model:open` to `true` once again).\n\nIs there a way I can make a Slideover not perform its default behavior of automatically closing when a click outside the Slideover _is a certain target or set of targets_? That way the Slideover will not close and immediately reopen, rather, it will stay open and just update to the newly specified content.\n\nThanks so much! I am very much enjoying building with Nuxt UI.",[3106,3109],{"name":3107,"color":3108},"question","d876e3",{"name":3110,"color":3111},"v3","49DCB8",4289,"Keep Slideover open when clicking specific targets outside","2025-06-05T16:50:38Z","https://github.com/nuxt/ui/issues/4289",0.7419153,{"description":3118,"labels":3119,"number":3121,"owner":3021,"repository":3035,"state":3048,"title":3122,"updated_at":3123,"url":3124,"score":3125},"Blocked by #405 ",[3120],{"name":3044,"color":3083},699,"[Company] Support carousel should use same images as landing page","2023-02-15T12:30:53Z","https://github.com/nuxt/nuxt.com/issues/699",0.7424179,["Reactive",3127],{},["Set"],["ShallowReactive",3130],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgpYl79R7MPU3yAJj9GMYu1t2yAjtCDE0KDCqOZgCqEQ":-1},"/nuxt/test-utils/681"]