` 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```",[3199,3200],{"name":3138,"color":3139},{"name":3155,"color":3156},2730,"USelectMenu | UInputMenu filter not working with value-key","2024-12-05T13:48:55Z","https://github.com/nuxt/ui/issues/2730",0.78576154,{"labels":3207,"number":3208,"owner":3141,"repository":3141,"state":3143,"title":3209,"updated_at":3210,"url":3211,"score":3212},[],12943,"Is there a plan for the internationalization of docs?","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12943",0.7864851,{"labels":3214,"number":3215,"owner":3141,"repository":3141,"state":3143,"title":3209,"updated_at":3216,"url":3217,"score":3212},[],13014,"2023-01-19T16:42:38Z","https://github.com/nuxt/nuxt/issues/13014",{"description":3219,"labels":3220,"number":3225,"owner":3141,"repository":3226,"state":3143,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v21.7.3\r\n- Nuxt Version: ^3.11.2\r\n- CLI Version: 3.13.1\r\n- Nitro Version: -\r\n- Package Manager: npm\r\n- Builder: - vite\r\n- User Config: compatibilityDate, devtools, modules, i18n\r\n- Runtime Modules: @pinia/nuxt@^0.5.1, @nuxt/test-utils/module@^3.13.1, @nuxt/devtools@^1.3.1, @nuxtjs/robots@^3.0.0, @nuxtjs/tailwindcss@^6.12.0, @nuxtjs/eslint-module@^4.1.0, @nuxtjs/i18n@^8.3.1, @vite-pwa/nuxt@^0.7.0, nuxt-clarity-analytics@^0.0.6, @nuxt/image@^1.7.0\r\n- Build Modules: -\r\n\n\n### Reproduction\n\nHere is reproduce, just try to install dependances.\r\n[@nuxt-test-utils-dependaces-error.zip](https://github.com/user-attachments/files/16807301/%40nuxt-test-utils-dependaces-error.zip)\n\n### Describe the bug\n\nnpm i catch npm ERR! ERESOLVE could not resolve\r\n\n\n### Additional context\n\nI reinstalled dependancy and caught error.\n\n### Logs\n\n```shell-script\nPS C:\\reproduce\\nuxt-autocomplit-type-error> npm i\r\nnpm ERR! code ERESOLVE\r\nnpm ERR! ERESOLVE could not resolve\r\nnpm ERR! \r\nnpm ERR! While resolving: nuxt-app@undefined\r\nnpm ERR! Found: vue@3.4.38\r\nnpm ERR! node_modules/vue\r\nnpm ERR! peer vue@\"^3.3.4\" from @nuxt/test-utils@3.14.1\r\nnpm ERR! node_modules/@nuxt/test-utils\r\nnpm ERR! dev @nuxt/test-utils@\"^3.13.1\" from the root project\r\nnpm ERR! peer vue@\"^3.2.0\" from vue-router@4.4.3\r\nnpm ERR! node_modules/vue-router\r\nnpm ERR! vue-router@\"^4.3.2\" from the root project\r\nnpm ERR! peer vue-router@\"^4.0.0\" from @nuxt/test-utils@3.14.1\r\nnpm ERR! node_modules/@nuxt/test-utils\r\nnpm ERR! dev @nuxt/test-utils@\"^3.13.1\" from the root project\r\nnpm ERR! 1 more (@nuxtjs/i18n)\r\nnpm ERR!\r\nnpm ERR! Could not resolve dependency:\r\nnpm ERR! dev @pinia/testing@\"^0.1.3\" from the root project\r\nnpm ERR!\r\nnpm ERR! Conflicting peer dependency: vue@2.6.14\r\nnpm ERR! node_modules/vue\r\nnpm ERR! peer vue@\">= 2.5 \u003C 2.7\" from @vue/composition-api@1.7.2\r\nnpm ERR! node_modules/@vue/composition-api\r\nnpm ERR! peerOptional @vue/composition-api@\"^1.4.0\" from pinia@2.2.2\r\nnpm ERR! node_modules/pinia\r\nnpm ERR! pinia@\"^2.1.7\" from the root project\r\nnpm ERR! 1 more (@pinia/testing)\r\nnpm ERR!\r\nnpm ERR! Fix the upstream dependency conflict, or retry\r\nnpm ERR! this command with --force or --legacy-peer-deps\r\nnpm ERR! to accept an incorrect (and potentially broken) dependency resolution.\r\nnpm ERR! \r\nnpm ERR!\r\nnpm ERR! For a full report see:\r\nnpm ERR! C:\\Users\\AppData\\Local\\npm-cache\\_logs\\2024-08-29T22_11_47_097Z-eresolve-report.txt\r\n\r\nnpm ERR! A complete log of this run can be found in: C:\\Users\\AppData\\Local\\npm-cache\\_logs\\2024-08-29T22_11_47_097Z-debug-0.log\n```\n",[3221,3222],{"name":3138,"color":3139},{"name":3223,"color":3224},"pending triage","5D08F5",928,"test-utils","Confilcts with @nuxt/test-utils and Nuxt3","2024-12-04T16:32:32Z","https://github.com/nuxt/test-utils/issues/928",0.78687555,{"description":3232,"labels":3233,"number":3236,"owner":3141,"repository":3142,"state":3143,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.37\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-mapbox@1.6.1, @nuxt/image@1.8.1, @nuxt/ui@3.0.0-alpha.10, @nuxtjs/supabase@1.4.5, @vueuse/nuxt@10.11.1, @nuxtjs/i18n@8.5.6, @vueuse/motion/nuxt@2.2.6\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n\u003CUTable\n :data=\"data\"\n :columns=\"columnsTable\"\n @select=\"select\"\n/>\n\n\n### Description\n\nIn Nuxt UI v3, the \u003CUTable /> component does not provide any trigger event when clicking on a table row. In contrast, the v2 version included the @select event, which allowed developers to handle row clicks effectively. This regression impacts the ability to implement common interaction patterns, such as handling row selection or performing actions based on user clicks.\n\nDoes Nuxt UI v3 have an event similar to the @select event from v2 for the \u003CUTable /> component? Specifically, is there a way to trigger an event when a table row is clicked?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3234,3235],{"name":3138,"color":3139},{"name":3155,"color":3156},3010,"UTable row click event UI3","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3010",0.78823036,["Reactive",3242],{},["Set"],["ShallowReactive",3245],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0Hjk4IcnhGzjOPjk_jR9uTr5EadXebN0AFVEOL1armA":-1},"/nuxt/nuxt.com/821"]