;\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CJsx />\n \u003CSomeOtherComponent />\n \u003C/div>\n\u003C/template>\n```\nthen the `\u003CJsx />` is replaced with `\u003Csomecomponent />` instead of the component body. \n\nManually importing `SomeComponent` (`import SomeComponent from '~/components/SomeComponent.vue'`) fixes the issue. I'd be happy to add these imports, but then it would be great if `npm run build` warned me about missing imports instead of silently creating a broken build. \n\nAdding `\u003CSomeOtherComponent />` to the example is necessary to reproduce the bug. The `\u003CJsx />` resolves correctly if the `\u003CSomeOtherComponent />` line is removed. \n\n### Additional context\n\nI've previously posted a slightly modified version of this issue on [Discord](https://discord.com/channels/473401852243869706/1337018462668587018/1337018462668587018). The Discord post was more a \"can anyone tell me what's going on?\" then a bug report, though, so I hope reposting here is okay. \n\n### Logs\n\n```shell-script\n\n```",[1984,1987],{"name":1985,"color":1986},"pending triage","E99695",{"name":1988,"color":1989},"nitro","bfd4f2",30929,"nuxt","open","Auto-import fails to import components used in JSX when building static site","2025-02-10T08:37:43Z","https://github.com/nuxt/nuxt/issues/30929",0.63251346,{"labels":1998,"number":2008,"owner":1991,"repository":1991,"state":2009,"title":2010,"updated_at":2011,"url":2012,"score":2013},[1999,2002,2005],{"name":2000,"color":2001},"3.x","29bc7f",{"name":2003,"color":2004},"bug","d73a4a",{"name":2006,"color":2007},"❗ p4-important","D93F0B",13429,"closed","Auto import of components broken","2023-01-19T16:55:49Z","https://github.com/nuxt/nuxt/issues/13429",0.5983547,{"labels":2015,"number":2021,"owner":1991,"repository":1991,"state":2009,"title":2022,"updated_at":2023,"url":2024,"score":2025},[2016,2017,2018],{"name":2000,"color":2001},{"name":1985,"color":1986},{"name":2019,"color":2020},"needs reproduction","FBCA04",13044,"Typescript composables ","2023-01-19T16:47:41Z","https://github.com/nuxt/nuxt/issues/13044",0.6060628,{"labels":2027,"number":2031,"owner":1991,"repository":1991,"state":2009,"title":2032,"updated_at":2033,"url":2034,"score":2035},[2028,2029,2030],{"name":2000,"color":2001},{"name":1985,"color":1986},{"name":2019,"color":2020},13932,"Take commented out code as import","2023-01-19T17:09:59Z","https://github.com/nuxt/nuxt/issues/13932",0.6174474,{"description":2037,"labels":2038,"number":2049,"owner":1991,"repository":1991,"state":2009,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### 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_",[2039,2040,2043,2046],{"name":2000,"color":2001},{"name":2041,"color":2042},"workaround available","11376d",{"name":2044,"color":2045},"upstream","E8A36D",{"name":2047,"color":2048},"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.6198001,{"labels":2055,"number":2060,"owner":1991,"repository":1991,"state":2009,"title":2061,"updated_at":2062,"url":2063,"score":2064},[2056,2057,2058],{"name":2000,"color":2001},{"name":2003,"color":2004},{"name":2059,"color":2020},"🔨 p3-minor",13337,"editing composables doesn't trigger regeneration of declarations","2023-01-19T17:03:07Z","https://github.com/nuxt/nuxt/issues/13337",0.62310416,{"description":2066,"labels":2067,"number":2071,"owner":1991,"repository":1991,"state":2009,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### 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",[2068,2069,2070],{"name":2000,"color":2001},{"name":1985,"color":1986},{"name":2019,"color":2020},15392,"Nuxt rc13 - Failed to resolve import","2023-01-19T17:49:29Z","https://github.com/nuxt/nuxt/issues/15392",0.62406766,{"description":2077,"labels":2078,"number":2081,"owner":1991,"repository":1991,"state":2009,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### 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_",[2079,2080],{"name":2000,"color":2001},{"name":1985,"color":1986},15317,"[vite-node] Failed to load...","2023-01-27T11:53:25Z","https://github.com/nuxt/nuxt/issues/15317",0.6262499,{"description":2087,"labels":2088,"number":2093,"owner":1991,"repository":1991,"state":2009,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-1wqbue-7nfm99?file=composables/useMain.ts\r\n\r\n```ts\r\nconst refMain = ref(null);\r\n\r\nexport default function useMain() {\r\n return {\r\n refMain,\r\n };\r\n}\r\n\r\n// export default function useMain() {\r\n// return {\r\n// refMain,\r\n// };\r\n// }\r\n```\r\n\r\nRemove the comments, restart the server, and it will work again.\n\n### Describe the bug\n\nThis took me a while to find out, but if you have a composable that has comments that contain the default export, Nuxt will break and won't be able to auto-import the composable\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2089,2090,2091,2092],{"name":2000,"color":2001},{"name":2003,"color":2004},{"name":2044,"color":2045},{"name":2059,"color":2020},14971,"Auto-import (composable) breaks when comments contain `export default function`","2023-01-19T17:43:10Z","https://github.com/nuxt/nuxt/issues/14971",0.62881356,{"labels":2099,"number":2102,"owner":1991,"repository":1991,"state":2009,"title":2103,"updated_at":2104,"url":2105,"score":2106},[2100,2101],{"name":2000,"color":2001},{"name":1985,"color":1986},14576,"RC-8 composables auto-imports regression for /composables/\u003Cfolder>/index.ts","2023-01-19T17:37:22Z","https://github.com/nuxt/nuxt/issues/14576",0.6296508,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"vHZf6qiPH_zLMx8hs2VD7Yw0adH-0bfAz3vZqFs7ZsE":-1},"/nuxt/nuxt/13573"]