\nI'd really appreciate it if the team considers a more flexible and intuitive API.\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://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2009,2010],{"name":1985,"color":1986},{"name":2011,"color":2012},"pending triage","E99695",29275,"Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.6912589,{"labels":2019,"number":2024,"owner":1991,"repository":1991,"state":2025,"title":2026,"updated_at":2027,"url":2028,"score":2029},[2020,2021],{"name":1985,"color":1986},{"name":2022,"color":2023},"2.x","d4c5f9",6517,"closed","Add example on how to use with @vue/composition-api","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6517",0.62611234,{"description":2031,"labels":2032,"number":2038,"owner":1991,"repository":1991,"state":2025,"title":2039,"updated_at":2040,"url":2041,"score":2042},"### Describe the feature\n\nI've been enjoying the DX of auto-imported components and composables ever since the release of those packages for Vue and I'm happy it's auto-configured for Nuxt.\r\n\r\nAs for the next step, would it be possible to **selectively** auto-import types? There's no point in auto-importing everything because large apps would just have too many types clogging the IDE and there would be naming collisions all over the place. But perhaps by adding a `.global` or `.auto` to a type file's name, exported types in those files could be safely auto-imported. It would certainly be a handy tool for those ubiquitous types that tend to sneak into many of your components.\r\n\r\nI'm sure there's pros and cons to this, so let's discuss 💬\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://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2033,2034,2037],{"name":1985,"color":1986},{"name":2035,"color":2036},"discussion","538de2",{"name":1988,"color":1989},27719,"Types auto-import","2024-08-09T09:39:34Z","https://github.com/nuxt/nuxt/issues/27719",0.6562231,{"labels":2044,"number":2053,"owner":1991,"repository":1991,"state":2025,"title":2054,"updated_at":2055,"url":2056,"score":2057},[2045,2046,2047,2050],{"name":1985,"color":1986},{"name":2035,"color":2036},{"name":2048,"color":2049},"3.x","29bc7f",{"name":2051,"color":2052},"dx","C39D69",11862,"`composables/` directory with auto discovery and import","2023-01-19T15:58:25Z","https://github.com/nuxt/nuxt/issues/11862",0.6585563,{"labels":2059,"number":2062,"owner":1991,"repository":1991,"state":2025,"title":2063,"updated_at":2064,"url":2065,"score":2066},[2060,2061],{"name":1985,"color":1986},{"name":2048,"color":2049},12790,"Support `global: false` for components","2023-01-19T16:35:12Z","https://github.com/nuxt/nuxt/issues/12790",0.6608569,{"description":2068,"labels":2069,"number":2075,"owner":1991,"repository":2076,"state":2025,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nI know you guys are working hard on V3, but I really like to see this feature still in V2. We all know that not everybody will move over to V3 right away.\n\nI have to set my `strategy` to `override`, because tailwind-merge doesn't know about my custom tailwind extends. This is quite a pain in the ass, since this is causing other issues as well. Take the [Pro LandingGird](https://ui.nuxt.com/pro/components/landing-grid) as example. Classes are added to the grid items to set the right cols. By doing this with `strategy` set to `override`, all other classes will be overridden.\n\nI saw some sort of solution in [#925 ](https://github.com/nuxt/ui/issues/925#issuecomment-1857910586), but that didn't work. It's also not documented and can't find it in the module either.\n\nI know have to create my own merge config, but that will not work for Nuxt UI.\n\n\n### Additional context\n\nYou may wonder why I need this. Thats because I'm also using Tailwind Fluid, and try to replicate a design library that uses different spacings etc.\n\n",[2070,2073],{"name":2071,"color":2072},"duplicate","cfd3d7",{"name":1985,"color":2074},"a2eeef",2893,"ui","Extend tailwind-merge configuration","2024-12-13T15:04:57Z","https://github.com/nuxt/ui/issues/2893",0.6717525,{"labels":2082,"number":2085,"owner":1991,"repository":1991,"state":2025,"title":2086,"updated_at":2087,"url":2088,"score":2089},[2083,2084],{"name":1985,"color":1986},{"name":2022,"color":2023},8667,"enable Vuex useStore import for Composition API","2023-01-22T15:52:45Z","https://github.com/nuxt/nuxt/issues/8667",0.67278904,{"description":2091,"labels":2092,"number":2095,"owner":1991,"repository":1991,"state":2025,"title":2096,"updated_at":2097,"url":2098,"score":2099},"- [x] Initial working version from [@nuxt/components](https://github.com/nuxt/components)\r\n- [x] `.dts` generation\r\n- [x] Decide about prefix\r\n- [x] Implement loader strategy (vite and webpack5) \r\n- [ ] Integrate with devtools\r\n\r\n### Discussion: Should we even have it with nuxt3?\r\n\r\nRelated tweet (https://twitter.com/youyuxi/status/1404795327144763398). I think that makes sense in many ways that auto-import is not that needed with new `\u003Cscript setup>` syntax and better VSCode integrations. But there are still some cases most notable, CMS/Content integrations that implicitly need global components. And also this gives possibility with nuxt devtools component playground\r\n\r\n### Discussion: Where to implement?\r\n\r\nIn `framework/packages/components` as a fork of `nuxt/components` and add by default in `nuxt3`\r\n\r\n### Discussion: Prefixing\r\n\r\nShould we use (by default) one level prefix `components/utils/bar/baz` => `BarBaz` or full prefix => `UtilsBarBaz` or not at all (`Baz`) by default (suggested by @Atinux). Second is much more future proof but less convenient for structuring components dir based on purpose (and atomic designs)",[2093,2094],{"name":2035,"color":2036},{"name":2048,"color":2049},11026,"Components Discovery","2023-01-19T14:46:30Z","https://github.com/nuxt/nuxt/issues/11026",0.6732588,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"TJtlRtAL0c40QVxL9xi_ggy4Tda9FsZnpmb6aj5Gbl4":-1},"/nuxt/nuxt/11813"]