\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).",[2887,2890],{"name":2888,"color":2889},"enhancement","8DEF37",{"name":2891,"color":2892},"pending triage","E99695",29275,"Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.6819282,{"description":2899,"labels":2900,"number":2910,"owner":2878,"repository":2878,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.5.3`\r\n- Nitro Version: `2.5.0`\r\n- Package Manager: `pnpm@8.6.2`\r\n- Builder: `vite`\r\n- User Config: `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nThis will result in an error because the type `Ref` is not found in `#imports`.\r\n```js\r\nimport { ref, type Ref } from '#imports'\r\n```\r\n\r\nor is this the correct approach..? (by the way I have set `autoImport: false` in `nuxt.config.ts`)\r\nActually, importing from 'vue' seems clearer to me than importing from '#imports'.\r\n```js\r\nimport { ref, type Ref } from 'vue'\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2901,2904,2907,2908,2909],{"name":2902,"color":2903},"types","2875C3",{"name":2905,"color":2906},"3.x","29bc7f",{"name":2869,"color":2870},{"name":2872,"color":2873},{"name":2875,"color":2876},21684,"closed","Can't import types like `Ref` from `#imports`","2023-06-26T15:53:31Z","https://github.com/nuxt/nuxt/issues/21684",0.6483195,{"description":2917,"labels":2918,"number":2927,"owner":2878,"repository":2878,"state":2911,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.16.0\n- Nuxt Version: 3.4.3\n- Nitro Version: 2.4.0\n- Package Manager: pnpm@8.5.0\n- Builder: vite\n- User Config: experimental, modules, colorMode\n- Runtime Modules: @unocss/nuxt@0.51.12, @vueuse/nuxt@10.1.2, nuxt-icon@0.4.0, nuxt-swiper@1.1.0, @nuxt/devtools@0.4.6, @nuxt/image-edge@1.0.0-28020728.5df24eb, @nuxtjs/color-mode@3.2.0\n- Build Modules: -\n\n### Reproduction\n\n\n\nThis error doesn't seem to be reproducible on Stackblitz so I have included a [github repo](https://github.com/tobychidi/nuxt-utils-import-error)\n\n### Describe the bug\n\nWhen functions are auto-imported from utils/ composables and used in Vue SFC Template, VsCode throws and error. Yes, I use the latest volar. This error appeared after `pnpm up` That bumped my Vue version to 3.3.1.\n\nI have not tried reverting Vue versions though. \n\n### Additional context\n\nExample: \n```\nProperty 'useShowSnack' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: { key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ref_for?: boolean | undefined; ... 8 more ...; style?: unknown; }; ... 10 more ...; $watch\u003CT extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (arg...'.ts(2339)\n```\n\n_No response_\n\n### Logs\n\n_No response_",[2919,2920,2921,2924],{"name":2905,"color":2906},{"name":2866,"color":2867},{"name":2922,"color":2923},"upstream","E8A36D",{"name":2925,"color":2926},"upstream-bug","B60205",20827,"TS Error with auto-imports from composables and utils in Vue Template after 3.3","2024-11-07T20:13:37Z","https://github.com/nuxt/nuxt/issues/20827",0.65579575,{"labels":2933,"number":2937,"owner":2878,"repository":2878,"state":2911,"title":2938,"updated_at":2939,"url":2940,"score":2941},[2934,2935,2936],{"name":2888,"color":2889},{"name":2902,"color":2903},{"name":2905,"color":2906},12808,"Auto import for types like `Ref`","2023-02-07T10:41:57Z","https://github.com/nuxt/nuxt/issues/12808",0.6586284,{"description":2943,"labels":2944,"number":2946,"owner":2878,"repository":2878,"state":2911,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v20.13.1\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.9.2\r\n- Builder: -\r\n- User Config: devtools, app, runtimeConfig, ssr, experimental, pwa, sourcemap, typescript, modules, vite, primevue, unocss, imports, googleFonts, turnstile, supabase, css, postcss\r\n- Runtime Modules: @nuxtjs/turnstile@0.9.3, @unocss/nuxt@0.61.5, nuxt-primevue@3.0.0, @nuxtjs/google-fonts@3.2.0, @nuxtjs/supabase@1.3.5, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.1, @vueuse/nuxt@10.11.0, @vite-pwa/nuxt@0.9.1 \r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-c1luxa?file=app.vue\n\n### Describe the bug\n\n```js\r\nconst regex =\r\n /^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*$/; //\r\n```\r\n\r\nOnce I use this regex anywhere in the script tag, all subsequent auto-imports stop working.\r\n\r\nSeriously, I often encounter this issue, especially when I write some content or comments within the template tags. Even though it fully complies with Vue's syntax, it causes compilation to fail until I either delete the content, change some words, or rewrite it differently. I don't understand the internal parsing logic of Nuxt or Vue3. This issue doesn't always happen, but it's quite common.\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2945],{"name":2891,"color":2892},28190,"The regex caused the auto-imports to fail.","2024-07-17T10:29:01Z","https://github.com/nuxt/nuxt/issues/28190",0.6586718,{"labels":2952,"number":2956,"owner":2878,"repository":2878,"state":2911,"title":2957,"updated_at":2958,"url":2959,"score":2960},[2953,2954,2955],{"name":2905,"color":2906},{"name":2872,"color":2873},{"name":2875,"color":2876},14242,"ref is not defined when import.meta.glob is used when template has an html class","2023-01-19T17:30:08Z","https://github.com/nuxt/nuxt/issues/14242",0.6619669,{"description":2962,"labels":2963,"number":2972,"owner":2878,"repository":2878,"state":2911,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Describe the feature\n\nHi, I'm not sure if this is a feature request or just a question, but I didn't find any related issues / docs.\r\n\r\n**Context:** \r\n\r\nI have an ESLint configuration and it contains rules [`no-undef`](https://eslint.org/docs/latest/rules/no-undef) and [`vue/no-undef-components`](https://eslint.vuejs.org/rules/no-undef-components.html) that report undeclared functions/variables/components.\r\n\r\n\r\n\r\nNuxt automatically imports many things and I like it, I don't want to import them explicitly.\r\n[This is slightly related issue](https://github.com/nuxt/nuxt.js/issues/13413), but I don't need to import them explicitly, I need an option to retrieve a **names** of all auto-imported components/functions to declare them as global in `.eslintrc` file.\r\n\r\n**My current workaround** is define them manually and declare as global like that:\r\n\r\n\r\n\r\nAlthough this is a working solution, there are some limitations:\r\n- It needs to be filled manually\r\n- It doesn't update automatically if I register a new module that adds a global component (such as `@nuxt/image`) or new composables (such as `@vueuse/nuxt`)\r\n- It doesn't update if I set custom dirs to import in `nuxt.config.ts` via `imports.dirs` and create a new file inside it.\r\n- It doesn't update if new release of Vue/Nuxt includes a new features\r\n\r\nSo, a lot of manual work every time something was changed.\r\nThis can be done using custom module, but I believe it should be done by Nuxt itself.\r\n\r\n**Feature request:**\r\n\r\nExpose an auto-imported functions / components names to allow import them and mark as global in `.eslintrc`\r\n\r\n\r\n\r\n**Additional info**\r\n\r\nI know it's recommended to disable `no-undef` for TypeScript at all, but currently, as far I know, there is no robust way to separate `\u003Cscript lang=\"ts\">` and `\u003Cscript>` in ESLint confgurations for `.vue` files. \r\n\r\nAlso Nuxt isn't only TypeScript framework. and global components still needs to be configured\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [X] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2964,2965,2968,2969],{"name":2888,"color":2889},{"name":2966,"color":2967},"good first issue","fbca04",{"name":2905,"color":2906},{"name":2970,"color":2971},"🍰 p2-nice-to-have","0E8A16",15015,"Retrieve auto-imported component / function names","2024-03-13T22:57:05Z","https://github.com/nuxt/nuxt/issues/15015",0.66530365,{"description":2978,"labels":2979,"number":2987,"owner":2878,"repository":2878,"state":2911,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.5.1\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: pnpm@8.7.1\r\n- Builder: -\r\n- User Config: modules, auth, security, typescript, devtools, i18n, postcss, tailwindcss, vue, vite\r\n- Runtime Modules: nuxt-security@0.14.4, @sidebase/nuxt-auth@0.5.0, @nuxtjs/tailwindcss@6.8.0, nuxt-svgo@3.5.0, @vueuse/nuxt@10.4.1, @nuxtjs/i18n@8.0.0-rc.4\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-xodh6t?file=modules%2Fexample%2Fpages%2Fsomething%2Findex.vue\n\n### Describe the bug\n\nThere are missing types from auto-imports, and that the ref, $fetch, or other variables are being inferred as `any` in modules.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2980,2981,2982,2983,2984,2985],{"name":2966,"color":2967},{"name":2902,"color":2903},{"name":2905,"color":2906},{"name":2872,"color":2873},{"name":2875,"color":2876},{"name":2986,"color":2967},"✨ good reproduction",22988,"Incorrect types of auto-imports in modules","2023-09-22T07:25:54Z","https://github.com/nuxt/nuxt/issues/22988",0.678008,{"labels":2993,"number":2999,"owner":2878,"repository":2878,"state":2911,"title":3000,"updated_at":3001,"url":3002,"score":3003},[2994,2995,2996],{"name":2905,"color":2906},{"name":2872,"color":2873},{"name":2997,"color":2998},"❗ p4-important","D93F0B",14615,"Auto import of `onMounted` is not working","2023-01-19T17:37:56Z","https://github.com/nuxt/nuxt/issues/14615",0.67822737,["Reactive",3005],{},["Set"],["ShallowReactive",3008],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuC6ZdKlMRNtQOB8GXff4PbqsqyQQeIufNKtGXkwxgzQ":-1},"/nuxt/nuxt/14882"]