\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n :value-key=\"undefined\"\n/>\n// will work but i need to handle label display manually using slot\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n/>\n```\n\n### Description\n\nI'm currently migrate my project to NuxtUi V3 and I have some issues with `\u003CUInputMenu />` and `\u003CUSelectMenu />`. On my selects I want to retrieve the full object selected so I don't set `value-key` but for display purpose I use the `label-key` props, however when I do this I get this typescript error on the `v-model` :\n```\nUnable to assign type 'User | undefined' to type 'string | undefined'.\nUnable to assign type 'User' to type 'string'. ts-plugin(2322)\n```\nAfter some research, I think the `label-key` alter the `value-key` type and that's what triggers the error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2930,2931,2934,2937],{"name":2916,"color":2917},{"name":2932,"color":2933},"v3","49DCB8",{"name":2935,"color":2936},"typescript","3A629E",{"name":2938,"color":2939},"triage","ffffff",3670,"ui","closed","v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.74339503,{"description":2948,"labels":2949,"number":2950,"owner":2905,"repository":2951,"state":2942,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.74770826,{"description":2957,"labels":2958,"number":2961,"owner":2905,"repository":2941,"state":2942,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.1.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @vueuse/nuxt@11.3.0, @nuxt/ui@3.0.0-alpha.9, @pinia/nuxt@0.5.5, nuxt-auth-sanctum@0.5.2, nuxt-i18n-micro@1.33.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/input-menu#value-key\n\n### Description\n\nIn components `\u003CUSelectMenu />` and `\u003CUInputMenu />` filter is not working when using an array of object and the \"value-key\" prop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2959,2960],{"name":2916,"color":2917},{"name":2932,"color":2933},2730,"USelectMenu | UInputMenu filter not working with value-key","2024-12-05T13:48:55Z","https://github.com/nuxt/ui/issues/2730",0.74868727,{"description":2967,"labels":2968,"number":2972,"owner":2905,"repository":2905,"state":2942,"title":2973,"updated_at":2974,"url":2975,"score":2976},"Similar like the folks @nodejs have done (https://github.com/nodejs/help), I think we could benefit if all the help related issues on _how to use_ nuxt (or one of its components) would be moved to a separate repo. Maybe even under @nuxt-community so more people can help, clean and resolve issues. But keep this tracker for bugs and features only.\r\n\r\nAlthough the nuxt-trinity :angel: tries to keep the tracker as clean as possible, I still find it quite confusing by time. If you look at the current first page there are only 4 bug/feature issues, the other 21 are all general help related.\r\nTake the memory leak issue currently in `rc11` as an example, there are two duplicate open issues about that (1695 and 1728), but they only appear on page __3__. I was surprised when yesterday 1984 appeared in which it was mentioned that the bug was (probably) solved already, while that is a great thing unfortunately nothing about that seems to be mentioned in the open issues 1695 or 1728. Probably that's partially caused because its just difficult now to keep track of all the bug issues?\r\n\r\nSplitting the help wanted issues into a separate repo should keep this issue tracker much cleaner so its easier:\r\n- for the nuxt-trinity to keep us informed about bug/feature statuses / progress\r\n- and for us users/developers to check if our issue has already been reported or not\r\n\r\nProbably we would need to add an `ISSUE_TEMPLATE` that explains this.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1770\">#c1770\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2969],{"name":2970,"color":2971},"2.x","d4c5f9",1995,"(proposal) Use this tracker for bugs/features only, move 'help wanted' to separate repo","2023-01-18T15:42:55Z","https://github.com/nuxt/nuxt/issues/1995",0.75183934,{"description":2978,"labels":2979,"number":2985,"owner":2905,"repository":2905,"state":2942,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Describe the feature\n\n一问:官网文档为什么这么卡呢?\r\n二问:官网文档为什么这么卡呢?\r\n三问:官网文档为什么这么卡呢?\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [X] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2980,2983],{"name":2981,"color":2982},"3.x","29bc7f",{"name":2919,"color":2984},"E99695",22599,"官网文档为什么这么卡呢?","2023-08-12T07:13:45Z","https://github.com/nuxt/nuxt/issues/22599",0.75839037,{"description":2991,"labels":2992,"number":2997,"owner":2905,"repository":2905,"state":2942,"title":2998,"updated_at":2999,"url":3000,"score":3001},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚 -->\n\n### Is your feature request related to a problem? Please describe.\n\n\u003C!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\n\n### Describe the solution you'd like\n\n\u003C!-- A clear and concise description of what you want to happen. Adding some code examples would be neat! -->\n\n### Describe alternatives you've considered\n\n\u003C!-- A clear and concise description of any alternative solutions or features you've considered. -->\n\n### Additional context\n\n\u003C!-- Add any other context or screenshots about the feature request here. -->\n",[2993,2996],{"name":2994,"color":2995},"enhancement","8DEF37",{"name":2970,"color":2971},9083,"Hi","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9083",0.75873727,{"labels":3003,"number":3006,"owner":2905,"repository":2905,"state":2942,"title":3007,"updated_at":2999,"url":3008,"score":3009},[3004,3005],{"name":2994,"color":2995},{"name":2970,"color":2971},9107,"Tu","https://github.com/nuxt/nuxt/issues/9107",0.7596159,{"description":3011,"labels":3012,"number":3020,"owner":2905,"repository":2905,"state":2942,"title":3021,"updated_at":3022,"url":3023,"score":3024},"### Describe the feature\n\nIt would be really great if you could publish changes ( fixes & features ) more often. \n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3013,3016,3019],{"name":3014,"color":3015},"documentation","5319e7",{"name":3017,"color":3018},"good first issue","fbca04",{"name":2981,"color":2982},12548,"Document Release Cycle","2023-03-07T17:46:27Z","https://github.com/nuxt/nuxt/issues/12548",0.7615942,["Reactive",3026],{},["Set"],["ShallowReactive",3029],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fsvSOyPVSlQYLEieFv19zo2oGBT4J4nPpJJyIslqR9BM":-1},"/nuxt/ui/2849"]