\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_",[2937],{"name":2938,"color":2939},"bug","d73a4a",2342,"ui","[SelectMenu] `creatable` bugged when not using `multiple`","2024-11-12T17:11:21Z","https://github.com/nuxt/ui/issues/2342",0.7698529,{"description":2947,"labels":2948,"number":2956,"owner":2910,"repository":2941,"state":2912,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.6.1`\r\n- Nuxt Version: `3.13.2`\r\n- CLI Version: `3.14.0`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `npm@10.8.3`\r\n- Builder: `-`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Version\n\n1.4.3\n\n### Reproduction\n\nhttps://test-docs-819.pages.dev/\n\n### Description\n\nI encountered a styling issue with Nuxt Content components when deploying a static site using `npm run generate`. Initially, I thought the issue was specific to my project, but after testing the Nuxt UI Pro docs template (without any custom modifications), the problem persisted.\r\n\r\nWhen deploying the site to Cloudflare as a static site, the Nuxt Content components lose their proper styling, leading to an unstyled or poorly styled appearance in production. This issue does not occur in development mode.\r\n\r\nSteps to reproduce:\r\n1. Use the Nuxt UI Pro documentation template.\r\n2. Deploy the site as a static site using `npm run generate`.\r\n3. Host the generated site on Cloudflare.\r\n\r\nExpected result:\r\nThe Nuxt Content components should maintain their correct styling in production.\r\n\r\nActual result:\r\nNuxt Content components appear unstyled or with incorrect styling when deployed.\r\n\r\nAny guidance or help with this issue would be appreciated!\r\n\r\n\n\n### Additional context\n\n\r\n\u003Cimg width=\"1273\" alt=\"Screenshot 2024-10-01 at 3 47 53 PM\" src=\"https://github.com/user-attachments/assets/7fbd2248-d933-4997-bdc8-49bdf05e3042\">\r\n\r\n---\r\n\r\n\u003Cimg width=\"1099\" alt=\"Screenshot 2024-10-01 at 3 49 32 PM\" src=\"https://github.com/user-attachments/assets/0b86db6b-8490-4b00-a884-31bf51d6802a\">\r\n\r\n---\r\n\r\n\u003Cimg width=\"943\" alt=\"Screenshot 2024-10-01 at 3 50 49 PM\" src=\"https://github.com/user-attachments/assets/9021d63a-bf13-4dbc-bae7-26f266eff554\">\r\n\r\n---\r\n\r\nTOC little icon appear only in small screens:\r\n\r\n\u003Cimg width=\"398\" alt=\"Screenshot 2024-10-01 at 3 52 00 PM\" src=\"https://github.com/user-attachments/assets/f4fe87ff-42d5-4584-a461-9d70fbbaf8c5\">\r\n\r\n\n\n### Logs\n\n```shell-script\nNo Logs\n```\n",[2949,2950,2953],{"name":2938,"color":2939},{"name":2951,"color":2952},"pro","5BD3CB",{"name":2954,"color":2955},"upstream","78bddb",2287,"Nuxt Content Components Not Styled Properly in Production with Static Site on Cloudflare","2024-10-02T10:16:24Z","https://github.com/nuxt/ui/issues/2287",0.7722868,{"description":2962,"labels":2963,"number":2965,"owner":2910,"repository":2911,"state":2912,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### 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_",[2964],{"name":2907,"color":2908},956,"registerEndpoint fails to register on deep paths","2024-11-26T16:14:09Z","https://github.com/nuxt/test-utils/issues/956",0.777244,{"description":2971,"labels":2972,"number":2973,"owner":2910,"repository":2911,"state":2912,"title":2974,"updated_at":2975,"url":2976,"score":2977},"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,"Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/451",0.78119755,{"description":2979,"labels":2980,"number":2985,"owner":2910,"repository":2941,"state":2912,"title":2986,"updated_at":2987,"url":2988,"score":2989},"",[2981,2982],{"name":2938,"color":2939},{"name":2983,"color":2984},"v3","49DCB8",2338,"[Tabs] Height shifts of 1px between `pill` and `link` variants","2024-10-28T09:49:02Z","https://github.com/nuxt/ui/issues/2338",0.7851316,{"description":2991,"labels":2992,"number":3000,"owner":2910,"repository":2941,"state":2912,"title":3001,"updated_at":3002,"url":3003,"score":3004},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2993,2994,2997],{"name":2938,"color":2939},{"name":2995,"color":2996},"documentation","0075ca",{"name":2998,"color":2999},"duplicate","cfd3d7",2429,"DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.78675413,{"description":3006,"labels":3007,"number":3011,"owner":2910,"repository":2921,"state":2912,"title":3012,"updated_at":3013,"url":3014,"score":3015},"Don't we have too many links in Community section compared to `Resources`, `Company`...?",[3008],{"name":3009,"color":3010},"question","ff1ab2",825,"[Community] Too many links","2022-11-17T11:43:46Z","https://github.com/nuxt/nuxt.com/issues/825",0.78781164,["Reactive",3017],{},["Set"],["ShallowReactive",3020],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdnfEDXWIiYgJms-geWfhhiG-c2zFwWQwu3hfMtu67FE":-1},"/nuxt/icon/323"]