\n```",[2020,2021],{"name":1996,"color":1997},{"name":1999,"color":2000},3517,"How To Style NavigationMenu items","2025-03-14T13:01:49Z","https://github.com/nuxt/ui/issues/3517",0.73514944,{"description":2028,"labels":2029,"number":2037,"owner":1985,"repository":2002,"state":2038,"title":2039,"updated_at":2040,"url":2041,"score":2042},"### Description\n\nWhen you set input type to file, there is no way to set the 'multiple' attribute \n\n### Additional context\n\n_No response_",[2030,2033,2034],{"name":2031,"color":2032},"enhancement","a2eeef",{"name":1999,"color":2000},{"name":2035,"color":2036},"triage","ffffff",3572,"closed","Adding multiple files support for Input","2025-03-18T11:24:32Z","https://github.com/nuxt/ui/issues/3572",0.67507726,{"description":2044,"labels":2045,"number":2046,"owner":1985,"repository":1986,"state":2038,"title":2047,"updated_at":2048,"url":2049,"score":2050},"There seems to be a bug with the integrations active class in header\r\n\r\nhttps://github.com/nuxt/nuxt.com/assets/38922203/d50705a7-ae7f-4317-ac3c-867d41ac76ac\r\n\r\n",[],1432,"Integration active class ","2023-11-22T14:26:00Z","https://github.com/nuxt/nuxt.com/issues/1432",0.70168144,{"description":2052,"labels":2053,"number":2057,"owner":1985,"repository":2002,"state":2038,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Environment\r\n\r\nnewest\r\n\r\n### Version\r\n\r\n^2.13.0\r\n\r\n### Reproduction\r\n\r\n`\u003CUTabs :ui=\"{strategy: 'override'}\">`\r\n\r\n### Description\r\n\r\nMake a UTabs component with an ui prop and set strategy as a string. Typescript will complain but it will render as intended\r\n\r\nTypes of property 'strategy' are incompatible.\r\nType 'string' is not assignable to type 'Strategy | undefined'\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2054],{"name":2055,"color":2056},"bug","d73a4a",2268,":ui prop typescript error with 'strategy' as a string","2024-09-30T09:51:02Z","https://github.com/nuxt/ui/issues/2268",0.7051694,{"description":2063,"labels":2064,"number":2067,"owner":1985,"repository":1986,"state":2038,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### Environment\n\nMacOS, Chrome, Firefox and Safari\n\n### Reproduction\n\n### to reproduce\n1.go to the a module category page with direct access, such as [security](https://nuxt.com/modules?category=Security) or [devtools](https://nuxt.com/modules?category=Devtools) or do a page refresh from any of the category page.\n2. open a bunch of module links in a NEW TAB via right click \"open in a new tab\" or CMD + Click\n3. find out that when you open a new link to a module, for instance, [nuxt-security](), the target URL that is actually opened is [nuxt-image](https://nuxt.com/modules/image)\n\n\nIt happens when opening a new tabs from the \"security\" category `?category=Security`\nIt only happens when opening the security category on direct access by typing accessing url directly\nIt does not happen when opening the link on the same window on the `?category=Security` page\nIt does not happen when opening links from [module page without category slug](https://nuxt.com/modules)\n\n\n\n### Describe the bug\n\nThere is a unpredictable behaviour. When i click on nuxt modules cards that links to Nuxt 3 modules on a new tab, it open a different link than the expected one.\n\nWhen I try direct access by clicking on the link (not a open in a new tab or CMD + Click , it works as expected\n\n### Additional context\n\n\n### additional info\nreproduced on Chrome and Safari.\nhttps://github.com/user-attachments/assets/0742a7fa-80c6-4556-b31c-26f181d9f92b\n\n### guess\n when browsing a category with an active filter, the opened links pattern (`@nuxtjs/kinde`, `@logto/nuxt`, `@nuxt/devtools `) actually match the links displayed on the [root main modules page](https://nuxt.com/modules) without active filter `https://nuxt.com/modules`.\n\n### Logs\n\n```shell-script\n\n```",[2065],{"name":2055,"color":2066},"ff281a",1750,"(nuxt website): module cards links are inconsistent at open new tab","2025-03-21T16:12:36Z","https://github.com/nuxt/nuxt.com/issues/1750",0.7112223,{"description":2073,"labels":2074,"number":2076,"owner":1985,"repository":1986,"state":2038,"title":2077,"updated_at":2078,"url":2079,"score":2080},"Related to VueUse:\n\n- https://github.com/vueuse/vueuse/issues/915\n- https://github.com/vueuse/vueuse/pull/1312",[2075],{"name":2055,"color":2066},151,"[VueUse] When pressing `CMD+K` and pressing `CMD` again, the action is triggered","2022-03-28T08:40:48Z","https://github.com/nuxt/nuxt.com/issues/151",0.715748,{"description":2082,"labels":2083,"number":2084,"owner":1985,"repository":2085,"state":2038,"title":2086,"updated_at":2087,"url":2088,"score":2089},"It would be really good to know why using `@nuxt/test-utils` is more beneficial than using `@vue/test-utils` in a Nuxt project. Despite the obvious point being this package is made specifically for Nuxt, `@vue/test-utils` still works perfectly well in Nuxt projects.\r\n\r\nCould we get some comparison docs (a table maybe) of what `@vue/test-utils` can't do for a Nuxt project, but `@nuxt/test-utils` can?",[],475,"test-utils","@nuxt/test-utils vs @vue/test-utils?","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/475",0.72051305,["Reactive",2091],{},["Set"],["ShallowReactive",2094],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"FFzz-GkiThPkfb63r15NvFjJynUG7lvLP8EGozOFBEU":-1},"/nuxt/test-utils/581"]