\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).",[1984,1987],{"name":1985,"color":1986},"enhancement","8DEF37",{"name":1988,"color":1989},"pending triage","E99695",29275,"nuxt","open","Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.6454297,{"description":1998,"labels":1999,"number":2004,"owner":1991,"repository":1991,"state":1992,"title":2005,"updated_at":2006,"url":2007,"score":2008},"### Describe the feature\n\nHey I am currently moving a big project from standard vue3 to nuxt, and have to rewrite most of my options api code to composition api..\r\n\r\nThe issue mostly is that some features are not there in composition api and when one is missing i can't \"link\" it to options api and then i got to go down the rabbit hole of changing my code to use composition api although it's already completely valid options api code.\r\n\r\nFor real, props, it is an awesome framework and it's very impressive etc.\r\n\r\nBUT.... in my opinion, it is kind of weird that it does not fully support vue (from my pov) as i do have to use so much \"special\" vue code instead of easily porting my app.\r\n\r\nI am still continuing to use nuxt for now but if you were able to make the transition a bit easier, i think a lot of people would use nuxt instead of plain old vue 3.\r\n\r\nI am willing to help with the adoption by saying what needs to happen (for a project like mine) to be easily portable to nuxt, if that is helpful.\r\n\r\nLmk what u think :) \n\n### Additional information\n\n- [X] 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).",[2000,2001],{"name":1985,"color":1986},{"name":2002,"color":2003},"馃嵃 p2-nice-to-have","0E8A16",21670,"Missing Support (Or documentation of) Options API with Nuxt","2024-06-30T11:08:29Z","https://github.com/nuxt/nuxt/issues/21670",0.6778684,{"labels":2010,"number":2018,"owner":1991,"repository":1991,"state":2019,"title":2020,"updated_at":2021,"url":2022,"score":2023},[2011,2012,2015],{"name":1985,"color":1986},{"name":2013,"color":2014},"3.x","29bc7f",{"name":2016,"color":2017},"dx","C39D69",12789,"closed","composable auto import improvements","2023-01-19T16:40:15Z","https://github.com/nuxt/nuxt/issues/12789",0.6227575,{"labels":2025,"number":2029,"owner":1991,"repository":1991,"state":2019,"title":2030,"updated_at":2031,"url":2032,"score":2033},[2026,2027,2028],{"name":1985,"color":1986},{"name":2013,"color":2014},{"name":2016,"color":2017},13383,"expose app and app types as `nuxt3/app`","2023-01-19T16:54:17Z","https://github.com/nuxt/nuxt/issues/13383",0.6246028,{"labels":2035,"number":2036,"owner":1991,"repository":1991,"state":2019,"title":2020,"updated_at":2037,"url":2038,"score":2039},[],12858,"2023-01-19T16:38:31Z","https://github.com/nuxt/nuxt/issues/12858",0.63409007,{"labels":2041,"number":2042,"owner":1991,"repository":1991,"state":2019,"title":2020,"updated_at":2043,"url":2044,"score":2039},[],12942,"2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12942",{"description":2046,"labels":2047,"number":2053,"owner":1991,"repository":1991,"state":2019,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### Environment\n\n\"nuxt\": \"^3.6.2\",\r\n\n\n### Reproduction\n\nHi!\r\nI try to add a composable under the composables folder and call it into a vue file.\n\n### Describe the bug\n\nIt returns 500 Not Defined\r\n\r\n\u003Cimg width=\"1047\" alt=\"Screenshot 2023-07-14 at 10 11 07\" src=\"https://github.com/nuxt/nuxt/assets/38940340/b6569e6f-10b3-453d-8a7d-3f688656bfb7\">\r\n\r\nThanks and kind regards,\r\n\r\nDavide\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2048,2049,2050],{"name":2013,"color":2014},{"name":1988,"color":1989},{"name":2051,"color":2052},"needs reproduction","FBCA04",22136,"Composables autoimport doesn't works in my \"nuxt\": \"^3.6.2\",","2023-10-20T10:59:25Z","https://github.com/nuxt/nuxt/issues/22136",0.6372381,{"description":2059,"labels":2060,"number":2065,"owner":1991,"repository":1991,"state":2019,"title":2066,"updated_at":2067,"url":2068,"score":2069},"Nuxt 3 uses Vue 3 with Composition API and [unjs/unctx](https://github.com/unjs/unctx) for supporting composables with the implicit context in nuxtApp (plugins, middleware) and nuxt kit too.\r\n\r\nHowever, there are many cases in this needs a better explanation of how it works internally to understand why an issue like [nuxt instance unavailable](https://github.com/nuxt/framework/issues?q=nuxt+instance+unavailable) happens and how to fix it with proper usage.\r\n\r\nI've made an outline story in https://github.com/nuxt/nuxt.js/issues/14269 which can probably be used as a basis to initiate this concept page.",[2061,2064],{"name":2062,"color":2063},"documentation","5319e7",{"name":2013,"color":2014},14723,"Document composables concept","2023-09-19T20:24:18Z","https://github.com/nuxt/nuxt/issues/14723",0.641555,{"description":2071,"labels":2072,"number":2077,"owner":1991,"repository":1991,"state":2019,"title":2078,"updated_at":2079,"url":2080,"score":2081},"- [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)",[2073,2076],{"name":2074,"color":2075},"discussion","538de2",{"name":2013,"color":2014},11026,"Components Discovery","2023-01-19T14:46:30Z","https://github.com/nuxt/nuxt/issues/11026",0.6455928,{"description":2083,"labels":2084,"number":2088,"owner":1991,"repository":1991,"state":2019,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### 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).",[2085,2086,2087],{"name":1985,"color":1986},{"name":2074,"color":2075},{"name":2002,"color":2003},27719,"Types auto-import","2024-08-09T09:39:34Z","https://github.com/nuxt/nuxt/issues/27719",0.6463524,["Reactive",2094],{},["Set"],["ShallowReactive",2097],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"JKcG6VA0h3qcYqv1m6zkDEXL6dw0CjlfOqcNEn6KMd0":-1},"/nuxt/nuxt/11862"]