\n \u003CNuxtWelcome />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconsole.log(\"111\");\n\u003C/script>\n```\n\n### Expected Behavior\nBuilt-in components should be auto-imported without errors during development.\n\n### Actual Behavior\nConsole errors occur for built-in components (e.g., `NuxtWelcome`), and auto-importing fails.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nWARN [Vue warn]: Failed to resolve component: NuxtRouteAnnouncer\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CApp> \n at \u003CNuxtRoot>\n\nthis is setup\n```",[2880],{"name":2881,"color":2882},"🔨 p3-minor","FBCA04",32290,"closed","[Bug] AutoImport Fails for Components with `vite.esbuild.minifyWhitespace=true` in Dev Mode","2025-06-06T04:42:30Z","https://github.com/nuxt/nuxt/issues/32290",0.6257263,{"description":2890,"labels":2891,"number":2898,"owner":2871,"repository":2871,"state":2884,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### Environment\n\n- Nuxi 3.0.0-rc.13 \r\n- Operating System: `Linux`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.13`\r\n- Nitro Version: `0.6.1`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `app`, `components`, `css`, `build`, `modules`, `apollo`, `postcss`, `vite`, `render`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.1.3`, `@nuxtjs/apollo@5.0.0-alpha.3`\r\n- Build Modules: `-`\n\n### Reproduction\n\n- \n\n### Describe the bug\n\nI created an app with nuxt 3 rc-13 based on a project running nuxt 3 rc-11. I copied the complete folder structure except .nuxt, node_modules, package.json and package-lock.json. I installed the modules @nuxtjs/tailwindcss@6.1.3 and @nuxtjs/apollo@5.0.0-alpha.3. \r\n\r\nAfter starting the app with `npm run dev` I got an error that the module `@vue/apollo-composable` is missing. This was because I forgot to remove the associated import statements in several vue files. After I removed the imports and set `apollo: { autoImports: true, ... }` in my nuxt.config nuxt still complains `[plugin:vite:import-analysis] Failed to resolve import \"@vue/apollo-composable\" from \"pages/[...pages].vue\". Does the file exist?` \r\n\r\nIt seems like vite or npm or some other unknown magic had cached my files and now still complains about imports in files that don't exist anymore... I double checked my files and removed all import statements related to `@vue/apollo-composable`. So what's happening there? \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\nERROR 13:14:48 [vite] Internal server error: Failed to resolve import \"@vue/apollo-composable\" from \"pages/[...pages].vue\". Does the file exist?\r\n Plugin: vite:import-analysis\r\n File: /home/aw/dev/ext/pages/[...pages].vue:5:27\r\n 3 | import { Head as __nuxt_component_2 } from \"/home/aw/dev/ext/node_modules/nuxt/dist/head/runtime/components\";\r\n 4 | import { useRoute, createError } from '#app';\r\n 5 | import { useQuery } from '@vue/apollo-composable';\r\n | ^\r\n 6 | import { useGetNodeByPath } from '~/composables/useMobileNav';\r\n 7 | import { useGetMeta } from '~/composables/useGetMeta';\r\n at formatError (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:39971:46)\r\n at TransformContext.error (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:39967:19)\r\n at normalizeUrl (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:36835:33)\r\n at async TransformContext.transform (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:36968:47)\r\n at async Object.transform (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:40224:30)\r\n at async loadAndTransform (file:///home/aw/dev/ext/node_modules/vite/dist/node/chunks/dep-51c4f80a.js:36611:29)\r\n\r\n[Vue Router warn]: uncaught error during route navigation:\r\nError: [vite-node] Failed to load @vue/apollo-composable\r\n at ViteNodeRunner.directRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:181:13)\r\n at runMicrotasks (\u003Canonymous>)\r\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\r\n at async ViteNodeRunner.cachedRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:129:12)\r\n at async request (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:152:16)\r\n at async /home/aw/dev/ext/pages/[...pages].vue:9:31\r\n at async ViteNodeRunner.directRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:250:5)\r\n at async ViteNodeRunner.cachedRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:129:12)\r\n at async request (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:152:16)\r\n at async /home/aw/dev/ext/node_modules/nuxt/dist/pages/runtime/router.mjs:75:94\r\n[Vue Router warn]: uncaught error during route navigation:\r\nError: [vite-node] Failed to load @vue/apollo-composable\r\n at ViteNodeRunner.directRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:181:13)\r\n at runMicrotasks (\u003Canonymous>)\r\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\r\n at async ViteNodeRunner.cachedRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:129:12)\r\n at async request (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:152:16)\r\n at async /home/aw/dev/ext/pages/[...pages].vue:9:31\r\n at async ViteNodeRunner.directRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:250:5)\r\n at async ViteNodeRunner.cachedRequest (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:129:12)\r\n at async request (file:///home/aw/dev/ext/node_modules/vite-node/dist/client.mjs:152:16)\r\n at async /home/aw/dev/ext/node_modules/nuxt/dist/pages/runtime/router.mjs:75:94\n```\n",[2892,2895,2896],{"name":2893,"color":2894},"3.x","29bc7f",{"name":2868,"color":2869},{"name":2897,"color":2882},"needs reproduction",15392,"Nuxt rc13 - Failed to resolve import","2023-01-19T17:49:29Z","https://github.com/nuxt/nuxt/issues/15392",0.62774086,{"description":2904,"labels":2905,"number":2912,"owner":2871,"repository":2871,"state":2884,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Environment\n\nnode: 16.13.2\r\nos: ubuntu 20.04\n\n### Reproduction\n\nnuxt.config.js\r\n\r\n`import { defineNuxtConfig } from 'nuxt/config'\r\nimport { resolve } from 'path'\r\n// import Components from 'unplugin-vue-components/vite'\r\n// import { ElementPlusResolver } from 'unplugin-vue-components/resolvers'\r\n// import AutoImport from 'unplugin-auto-import/vite'\r\n\r\n// import AutoImport from 'unplugin-auto-import/vite'\r\nimport Components from 'unplugin-vue-components/vite'\r\nimport { ElementPlusResolver } from 'unplugin-vue-components/resolvers'\r\n// import ElementPlus from \"unplugin-element-plus/vite\"\r\n\r\nexport default defineNuxtConfig({\r\n vite: {\r\n ssr: {\r\n noExternal: [\"element-plus/es\"],\r\n },\r\n plugins: [\r\n Components({\r\n resolvers: [ElementPlusResolver()],\r\n }),\r\n // AutoImport({\r\n // // imports: ['@element-plus/icons-vue'],\r\n // })\r\n ],\r\n resolve: {\r\n extensions: ['.mjs', '.js', '.ts', '.jsx', '.tsx', '.json', '.vue'],\r\n alias: {\r\n fs: require.resolve('rollup-plugin-peer-deps-external')\r\n }\r\n }\r\n },\r\n alias: {\r\n 'element-plus/dist/index.css': resolve(__dirname, './node_modules/element-plus/dist/index.css')\r\n },\r\n modules: ['@element-plus/nuxt'],\r\n compilerOptions: {\r\n isCustomElement: (tag) => ['el-'].includes(tag),\r\n }\r\n})\r\n`\r\nI have tried everything in all the forums\r\n\n\n### Describe the bug\n\nI have published a component in npm called survey-components which has SurveyPreview.vue component which uses element-plus, I have build this package with vite and externalize element-plus and published it. While consuming this SurveyPreview component in nuxt 3 app, element-plus tags like el-row, el-col and etc used in SurveyPreview component are Failed to resolve component.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2906,2907,2908,2909],{"name":2893,"color":2894},{"name":2868,"color":2869},{"name":2897,"color":2882},{"name":2910,"color":2911},"closed-by-bot","ededed",23439,"Nuxt 3 vite + element-plus doesn't compile element-plus tags when importing component from npm packages","2023-10-05T01:48:37Z","https://github.com/nuxt/nuxt/issues/23439",0.6300125,{"description":2918,"labels":2919,"number":2922,"owner":2871,"repository":2871,"state":2884,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nMinimal Reproduction that _\"extends\"_ **ui** folder.\r\nhttps://stackblitz.com/edit/nuxt-framework-ikip96?file=pages/index.vue\r\n\r\n### Describe the bug\r\n\r\nI am trying to use the extends feature within the Nuxt config but for some reason, it fails to load the components from within that folder: https://v3.nuxtjs.org/examples/advanced/config-extends\r\n\r\nI am intentionally _not_ using auto-imported components and am instead _explicitly_ importing them.\r\n\r\n```vue\r\n\u003Cscript setup>\r\nimport FancyButton from '@/components/FancyButton.vue'; // This is in the main app.\r\nimport MyList from '@/components/MyList.vue'; // This is in the 'extended' folder (./ui/components/MyList.vue)\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CFancyButton>Fancy Button\u003C/FancyButton>\r\n \u003CMyList>List\u003C/MyList>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nI was of the understanding that by extending a folder, components and other assets would be available as if in the same location as the consuming app. I think this is a bug but I could be wrong?\r\n\r\nCould it be something to do with import aliases like @? On the reproduction I'm getting:\r\n\r\n```\r\n500\r\n[vite-node] Failed to load /components/MyList.vue\r\nat directRequest (./node_modules/vite-node/dist/client.mjs:198:13)\r\nat ()\r\n```\r\n\r\n### Additional context\r\n\r\nI had someone look at the minimal reproduction and they got it working by removing explicit imports and only using the auto-imports. However, we cannot do this within our app because our unit tests do not know what the components are otherwise, so this is why we always import them manually. But in any case, this should still work, right?\r\n\r\n### Logs\r\n\r\n_No response_",[2920,2921],{"name":2893,"color":2894},{"name":2868,"color":2869},15317,"[vite-node] Failed to load...","2023-01-27T11:53:25Z","https://github.com/nuxt/nuxt/issues/15317",0.6443642,{"description":2928,"labels":2929,"number":2932,"owner":2871,"repository":2871,"state":2884,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.8.1\r\n- Builder: -\r\n- User Config: modules, myModule, devtools\r\n- Runtime Modules: ../src/module\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/MooseSaeed/my-module/blob/master/src/module.ts\r\n\r\n### Describe the bug\r\n\r\nThe `addPluginTemplate()` in `@nuxt/kit` throws the below error to the console when importing `defineNuxtPlugin` from `#imports`:\r\n\r\n```\r\n[nuxt] `#imports` should be transformed with real imports. There seems to be something wrong with the imports plugin.\r\n```\r\n\r\nThe error goes away if I import `defineNuxtPlugin` from `#app` instead of `#imports` even though the [documentation's example](https://nuxt.com/docs/api/kit/plugins#addplugintemplate) is using `#imports`\r\n\r\nAlso the error doesn't occur with `npx nuxi build`. It only shows up by running dev. \r\n\r\n### Additional context\r\n\r\nDidn't raise the issue on module-builder or Module Starter Template because the issue is happening when using local modules too.\r\n\r\n### Logs\r\n\r\n```shell-script\r\nTEST Plugin Template - build time 7:37:13 PM\r\nℹ Vite client warmed up in 372ms 7:37:14 PM\r\nℹ Vite server warmed up in 546ms 7:37:14 PM\r\n✔ Nitro built in 248 ms nitro 7:37:14 PM\r\n[nuxt] `#imports` should be transformed with real imports. There seems to be something wrong with the imports plugin.\r\nTEST Plugin Template\r\n```\r\n```\r\n",[2930,2931],{"name":2893,"color":2894},{"name":2868,"color":2869},24733,"Getting error from Nuxt when using #imports in a plugin template","2024-01-02T15:35:22Z","https://github.com/nuxt/nuxt/issues/24733",0.6461153,{"labels":2938,"number":2942,"owner":2871,"repository":2871,"state":2884,"title":2943,"updated_at":2944,"url":2945,"score":2946},[2939,2940,2941],{"name":2893,"color":2894},{"name":2868,"color":2869},{"name":2897,"color":2882},13573,"[Hard to reproduce] Issue with auto-import of composables in some components","2023-01-19T16:59:51Z","https://github.com/nuxt/nuxt/issues/13573",0.64697224,{"description":2948,"labels":2949,"number":2952,"owner":2871,"repository":2871,"state":2884,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Environment\r\n\r\nRootDir: /home/projects/github-zxwxk5-aqc6tg \r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: modules, components\r\n- Runtime Modules: @rah-emil/vite-plugin-vue-type-imports/nuxt@0.2.5\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n\r\nHere is reproduction, there are two components. \r\n`components/DemoWork.vue` - it uses `MyInterface` imported from types and it works\r\n`components/globals/Demo.vue` - it uses `MyInterface` imported from types and it doest not work\r\n\r\none difference is the `components/globals/Demo` is attached by autoimport\r\n\r\nTo run project properly you have to comment nuxt.config.ts\r\n```js\r\n components: [{ path: '~/components/globals', global: true }, '~/components'],\r\n```\r\nhttps://stackblitz.com/edit/github-zxwxk5-aqc6tg?file=components/globals/Demo.vue\r\n\r\n### Describe the bug\r\n\r\nWe are using a plugin (https://github.com/rah-emil/vite-plugin-vue-type-imports/blob/main/src/core/index.ts) for Vite that allows us to import external types as component props interfaces. However, in version 3.4.3, we noticed that the plugin still works but global components attached by autoimport no longer work.\r\n\r\nCan we do something about this? Our library uses global components with imported types and now we have regression. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2950,2951],{"name":2893,"color":2894},{"name":2868,"color":2869},20720,"Global components attached by autoimports do not respect the Vite plugin (3.4.3)","2023-05-22T07:04:36Z","https://github.com/nuxt/nuxt/issues/20720",0.64707863,{"labels":2958,"number":2966,"owner":2871,"repository":2871,"state":2884,"title":2967,"updated_at":2968,"url":2969,"score":2970},[2959,2960,2963],{"name":2893,"color":2894},{"name":2961,"color":2962},"bug","d73a4a",{"name":2964,"color":2965},"❗ p4-important","D93F0B",13429,"Auto import of components broken","2023-01-19T16:55:49Z","https://github.com/nuxt/nuxt/issues/13429",0.6479912,{"description":2972,"labels":2973,"number":2978,"owner":2871,"repository":2871,"state":2884,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.7.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `modules`, `css`, `colorMode`, `vite`, `app`\r\n- Runtime Modules: `nuxt-windicss@2.5.0`, `@pinia/nuxt@0.3.1`, `@nuxtjs/color-mode@3.1.4`, `@nuxt/image-edge@1.0.0-27657146.da85542`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-izskfd?file=components/Book.vue\r\n\r\n### Describe the bug\r\n\r\nuseRoute(), nuxt default provided function, has previous route information, and not updated on moving page.\r\n\r\nBut using `import { useRoute } from vue-router`, resolve all problems.\r\n\r\nIs there any point I missed?\r\n\r\n### Additional context\r\n\r\nrc.6 doesn't have problems but rc.8 has.\r\n\r\nIt just occurred as soon as updating from rc.6 to rc.8\r\n\r\n### Logs\r\n\r\n_No response_",[2974,2977],{"name":2975,"color":2976},"documentation","5319e7",{"name":2881,"color":2882},14595,"auto-imported `useRoute()` from nuxt requires use of `\u003CNuxtPage>`","2025-06-03T13:52:48Z","https://github.com/nuxt/nuxt/issues/14595",0.6480178,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$flNLVXqC097RFK7wUu9hxVUyYOszjtcLVVYue5VfGbHk":-1},"/nuxt/ui/4113"]