\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_",[2920],{"name":2921,"color":2922},"bug","d73a4a",2342,"closed","[SelectMenu] `creatable` bugged when not using `multiple`","2024-11-12T17:11:21Z","https://github.com/nuxt/ui/issues/2342",0.70501393,{"description":2930,"labels":2931,"number":2932,"owner":2868,"repository":2933,"state":2924,"title":2934,"updated_at":2935,"url":2936,"score":2937},"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":2939,"labels":2940,"number":2941,"owner":2868,"repository":2942,"state":2924,"title":2943,"updated_at":2944,"url":2945,"score":2946},"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":2948,"labels":2949,"number":2950,"owner":2868,"repository":2912,"state":2924,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### 📚 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":2956,"labels":2957,"number":2963,"owner":2868,"repository":2912,"state":2924,"title":2964,"updated_at":2965,"url":2966,"score":2967},"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",[2958,2960],{"name":2921,"color":2959},"ff281a",{"name":2961,"color":2962},"responsive","1cd1c6",817,"[Resources] Live events responsive issues","2023-02-15T12:31:00Z","https://github.com/nuxt/nuxt.com/issues/817",0.72919625,{"description":2969,"labels":2970,"number":2974,"owner":2868,"repository":2933,"state":2924,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### 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_",[2971],{"name":2972,"color":2973},"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,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgpYl79R7MPU3yAJj9GMYu1t2yAjtCDE0KDCqOZgCqEQ":-1},"/nuxt/test-utils/681"]