\n\u003C/template>\n```\n\n2. Notice that the USelectMenu remains blank despite the initial value being set to `0`.\n\n**Expected Behavior:** \nThe USelectMenu should correctly bind and display the option corresponding to the numeric value `0`.\n\nCould you please consider looking into this issue so that numeric `0` is handled correctly, similar to how `false` is now working?\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[2885,2888],{"name":2886,"color":2887},"bug","d73a4a",{"name":2872,"color":2873},3392,"USelectMenu: Numeric value 0 causes binding issue","2025-02-25T06:47:48Z","https://github.com/nuxt/ui/issues/3392",0.78624576,{"description":2895,"labels":2896,"number":2898,"owner":2875,"repository":2899,"state":2877,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.13.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.5.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.7.2, nuxt-open-fetch@0.9.5, @nuxtjs/i18n@9.1.0, nuxt-jsonld@2.1.0, @nuxtjs/device@3.2.4, @nuxtjs/robots@5.0.0, @vueuse/nuxt@12.0.0, @sidebase/nuxt-auth@0.9.4, @vesp/nuxt-fontawesome@1.1.0\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nWhen using a vitest workspace, vitest complains that it can't resolve the config files, this is due to `defineVitestConfig`.\n```\n> vitest\n\nfailed to load config from /Users/reinierkaper/rvezy/rvezy-web-client/src/tests/unit/vitest.config.ts\n```\n\n### Describe the bug\n\nI think the `defineVitestConfig` wrapper conflicts with what vitest expects back in a workspace configuration file.\nEverything works fine when the tests are ran directly with a config file reference, just not in a workspace.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2897],{"name":2886,"color":2887},1043,"test-utils","Vitest workspaces not properly supported by `defineVitestConfig`","2025-02-21T09:20:04Z","https://github.com/nuxt/test-utils/issues/1043",0.8001151,{"description":2905,"labels":2906,"number":2911,"owner":2875,"repository":2876,"state":2912,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Description\n\nI've recently upgraded to NuxtUi [v3.0.2](https://github.com/nuxt/ui/releases/tag/v3.0.2) from [v3.0.0-beta.2](https://github.com/nuxt/ui/releases/tag/v3.0.0-beta.2) and I'm having an issue with the search term prop on the component.\n\nWhen using the input with search and multiselect, I'd like the search term to clear as the user selects menu items. I was able to achieve this, in previous versions, by using a v-model on the search term and calling a function to clear the search term on the `update:ModelValue` event. Unfortunately, this isn't working on the most recent version.\n\nIt appears that `update:ModelValue` is being emitted and I am able to clear the searchTerm ref value. However, the change doesn't propagate to the component unless I hit the tab key or click out and click back into the component.\n\nIs there a potential workaround or could this become a feature request to include a prop which clears the search term on item select?",[2907,2910],{"name":2908,"color":2909},"question","d876e3",{"name":2869,"color":2870},3782,"closed","InputMenu Clear Search Term on Select","2025-04-08T10:37:15Z","https://github.com/nuxt/ui/issues/3782",0.767222,{"description":2918,"labels":2919,"number":2924,"owner":2875,"repository":2876,"state":2912,"title":2925,"updated_at":2926,"url":2927,"score":2928},"https://reka-ui.com/docs/guides/migration",[2920,2923],{"name":2921,"color":2922},"feature","A27AF6",{"name":2869,"color":2870},2259,"Migrate to Reka UI, the new Radix Vue","2024-12-03T15:11:33Z","https://github.com/nuxt/ui/issues/2259",0.77602226,{"description":2930,"labels":2931,"number":2932,"owner":2875,"repository":2933,"state":2912,"title":2934,"updated_at":2935,"url":2936,"score":2937},"- [x] Colors & Fonts\n- [x] Landing page (Home)\n- [x] Showcase categories/hero\n- [x] Modules categories/hero\n- [x] Blog categories/hero\n- [x] Support hero/content",[],1305,"nuxt.com","Marketing Update","2023-07-04T10:00:31Z","https://github.com/nuxt/nuxt.com/issues/1305",0.79005647,{"description":2939,"labels":2940,"number":2944,"owner":2875,"repository":2876,"state":2912,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Description\n\nWhile most components support the theming props (globally via app.config and as local props) the UForm component doesn't. For consistency it'd be great if this could be added to the Form component too.\n\n### Additional context\n\n_No response_",[2941,2942,2943],{"name":2866,"color":2867},{"name":2869,"color":2870},{"name":2872,"color":2873},3752,"Form Component: Support theming props","2025-04-10T19:55:39Z","https://github.com/nuxt/ui/issues/3752",0.79066813,{"description":2950,"labels":2951,"number":2954,"owner":2875,"repository":2876,"state":2912,"title":2955,"updated_at":2956,"url":2957,"score":2958},"Tested with latest `https://pkg.pr.new/@nuxt/ui@18931ac`",[2952,2953],{"name":2886,"color":2887},{"name":2869,"color":2870},2602,"[v3] `useLocale` missing import in various components","2024-11-11T18:27:39Z","https://github.com/nuxt/ui/issues/2602",0.7918695,{"description":2960,"labels":2961,"number":2964,"owner":2875,"repository":2876,"state":2912,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nI appreciate new version 3 of NuxtUI very much.\n\nOn production build of my recent app, it seems to take too much time (~5s) to SSR every page.\nSome pages does not fetch any data, so I wondered if NuxtUI or TailwindCSS were responsible for that.\n(Lighthouse score was very fine, by the way)\n\nThe app had neither dependencies of `tailwindcss` nor `@tailwindcss/vite` in package.json, so I installed them to try to improve first show speed.\nSurprisingly, it worked and showed quickly (~1s). The problem now fixed.\n\nIt is friendly for developers that NuxtUI requires TailwindCSS packages because it contains the dependencies in it.\nHowever, I don't think that the capability of NuxtUI is fully delivered without `@tailwindcss/vite`.\nI wish some internal implementation around this problem would be identified to get refined. Thank you.\n\nHere is the app before/after installing `tailwindcss` and `@tailwindcss/vite` (excuse me it's Japanese only):\n\n- Before: https://67e0d5d81fdcb30008c12162--dodoi2.netlify.app/\n- After: https://67efec8e3667f0000841d4df--dodoi2.netlify.app/",[2962,2963],{"name":2908,"color":2909},{"name":2869,"color":2870},3792,"Rendering is too slow unless installing `@tailwindcss/vite` as well?","2025-04-06T10:26:23Z","https://github.com/nuxt/ui/issues/3792",0.7932042,{"description":2970,"labels":2971,"number":2973,"owner":2875,"repository":2876,"state":2912,"title":2974,"updated_at":2975,"url":2976,"score":2977},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[2972],{"name":2869,"color":2870},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.79390055,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjzZ-Bn0ZTdh4rMt65h7EqPCkvzrU1uViA9Afloomm1g":-1},"/nuxt/ui/2317"]