\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).",[3018,3021],{"name":3019,"color":3020},"enhancement","8DEF37",{"name":3022,"color":3023},"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.64939064,{"description":3032,"labels":3033,"number":3038,"owner":3025,"repository":3025,"state":3026,"title":3039,"updated_at":3040,"url":3041,"score":3042},"### Describe the feature\r\n\r\nA common practice is to separate the logic between files and keep the test files together with the code.\r\nI suggest to scan index files within the subdirectories for composables, utils and middlewares by default, how it is currently done for modules and plugins (but is deprecated https://github.com/nuxt/nuxt/issues/25331 😞 ), where the auto-registered files patterns are:\n\n```sh\nmodules/*/index.ts\nmodules/*.ts\n```\r\n\r\n### Motivation:\r\nI recently created another Nuxt project and without suspecting it, created a folder with an index file inside composables, but of course it did not work. So I had to do what I do for all new Nuxt projects::\r\n```ts\r\n dirs: [\r\n 'composables/*/*.ts',\r\n 'utils/*/*.ts'\r\n ],\r\n```\r\n\r\nWhich seems unnatural and, to me, doesn't really fit with Nuxt's title — \"The **Intuitive** Vue framework.\"\r\nThe typical folders structure I usually work with:\r\n```sh\r\ncomposables/\r\n useHost/\r\n tests\r\n index.ts\r\n useMask/\r\n tests\r\n index.ts\r\n...\r\n```\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3034,3035],{"name":3019,"color":3020},{"name":3036,"color":3037},"workaround available","11376d",25831,"Scan index files within subdirectories for composables, utils and middlewares","2024-06-30T11:05:44Z","https://github.com/nuxt/nuxt/issues/25831",0.67412806,{"labels":3044,"number":3052,"owner":3025,"repository":3025,"state":3053,"title":3054,"updated_at":3055,"url":3056,"score":3057},[3045,3046,3049],{"name":3019,"color":3020},{"name":3047,"color":3048},"3.x","29bc7f",{"name":3050,"color":3051},"dx","C39D69",12789,"closed","composable auto import improvements","2023-01-19T16:40:15Z","https://github.com/nuxt/nuxt/issues/12789",0.6153614,{"labels":3059,"number":3060,"owner":3025,"repository":3025,"state":3053,"title":3054,"updated_at":3061,"url":3062,"score":3063},[],12858,"2023-01-19T16:38:31Z","https://github.com/nuxt/nuxt/issues/12858",0.6264642,{"labels":3065,"number":3066,"owner":3025,"repository":3025,"state":3053,"title":3054,"updated_at":3067,"url":3068,"score":3063},[],12942,"2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12942",{"labels":3070,"number":3074,"owner":3025,"repository":3025,"state":3053,"title":3075,"updated_at":3076,"url":3077,"score":3078},[3071,3072,3073],{"name":3019,"color":3020},{"name":3047,"color":3048},{"name":3050,"color":3051},13383,"expose app and app types as `nuxt3/app`","2023-01-19T16:54:17Z","https://github.com/nuxt/nuxt/issues/13383",0.62808186,{"description":3080,"labels":3081,"number":3089,"owner":3025,"repository":3025,"state":3053,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### 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).",[3082,3083,3086],{"name":3019,"color":3020},{"name":3084,"color":3085},"discussion","538de2",{"name":3087,"color":3088},"🍰 p2-nice-to-have","0E8A16",27719,"Types auto-import","2024-08-09T09:39:34Z","https://github.com/nuxt/nuxt/issues/27719",0.6473772,{"description":3095,"labels":3096,"number":3101,"owner":3025,"repository":3025,"state":3053,"title":3102,"updated_at":3103,"url":3104,"score":3105},"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.",[3097,3100],{"name":3098,"color":3099},"documentation","5319e7",{"name":3047,"color":3048},14723,"Document composables concept","2023-09-19T20:24:18Z","https://github.com/nuxt/nuxt/issues/14723",0.6512826,{"description":3107,"labels":3108,"number":3114,"owner":3025,"repository":3025,"state":3053,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### 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_",[3109,3110,3111],{"name":3047,"color":3048},{"name":3022,"color":3023},{"name":3112,"color":3113},"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.65416396,{"description":3120,"labels":3121,"number":3124,"owner":3025,"repository":3025,"state":3053,"title":3125,"updated_at":3126,"url":3127,"score":3128},"- [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)",[3122,3123],{"name":3084,"color":3085},{"name":3047,"color":3048},11026,"Components Discovery","2023-01-19T14:46:30Z","https://github.com/nuxt/nuxt/issues/11026",0.6547203,["Reactive",3130],{},["Set"],["ShallowReactive",3133],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJKcG6VA0h3qcYqv1m6zkDEXL6dw0CjlfOqcNEn6KMd0":-1},"/nuxt/nuxt/11862"]