\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nwithDefaults(\r\n defineProps\u003C{\r\n variant: \"fill\" | \"ghost\";\r\n }>(),\r\n { variant: \"fill\" }\r\n);\r\n\u003C/script>\r\n```\r\n\r\n`~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\ndeclare module 'vue' {\r\n export interface GlobalComponents {\r\n //...\r\n 'MyButton': typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n //...\r\n }\r\n}\r\n\r\nexport const MyButton: typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n\r\nexport const componentNames: string[]\r\n```\r\n\r\n\r\n### Correct Intellisense\r\n\r\nVsCode popopver hovering `'MyButton'` in `~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\n(property) GlobalComponents['MyButton']: __VLS_WithTemplateSlots\u003CDefineComponent\u003C{\r\n variant: {\r\n type: PropType\u003C\"fill\" | \"ghost\">;\r\n required: true;\r\n default: string;\r\n };\r\n}, {}, unknown, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, ... 5 more ..., {}>, {\r\n ...;\r\n}>\r\n````\r\n\r\n### Wrong Intellisense\r\n\r\nVsCode popopver hovering `\u003CMyButton />` in the template block of `~/app.vue` (or any other template)\r\n\r\n```TypeScript\r\n(property) 'MyButton': DefineComponent\u003C{}, {}, any>\r\n```\r\n\r\n### Additional context\r\n\r\nThe above example is the current state of the reproduction repo. But a different, but similar behavior happened in other reports (for example a yarn workspace repo). Strange enough, sometimes, it works fine...\r\n\r\n### Logs\r\n\r\n_No response_",[2052,2053,2054,2055],{"name":2031,"color":2032},{"name":2004,"color":2005},{"name":1985,"color":1986},{"name":1988,"color":1989},21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6303422,{"labels":2062,"number":2065,"owner":1991,"repository":1991,"state":2013,"title":2066,"updated_at":2067,"url":2068,"score":2069},[2063,2064],{"name":2004,"color":2005},{"name":2007,"color":2008},12005,"nuxt3 does not export NuxtConfig","2023-01-19T16:03:31Z","https://github.com/nuxt/nuxt/issues/12005",0.6352149,{"description":2071,"labels":2072,"number":2081,"owner":1991,"repository":1991,"state":2013,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.15.1\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.27\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-hxerk6?file=app.tsx\n\n### Describe the bug\n\nComponents types are not being auto imported when working with `tsx` files instead `vue`. (But they render ok)\r\nFor example I get: `Cannot find name 'NuxtLink'.`\r\nBut if I import the `NuxtLink` from `#components` manually I get the typings.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2073,2074,2075,2078],{"name":2031,"color":2032},{"name":2007,"color":2008},{"name":2076,"color":2077},"🔨 p3-minor","FBCA04",{"name":2079,"color":2080},"✨ good reproduction","fbca04",28781,"(tsx) Auto imports typings","2024-09-02T11:02:48Z","https://github.com/nuxt/nuxt/issues/28781",0.6355589,{"labels":2087,"number":2096,"owner":1991,"repository":1991,"state":2013,"title":2097,"updated_at":2098,"url":2099,"score":2100},[2088,2089,2090,2093],{"name":2004,"color":2005},{"name":2007,"color":2008},{"name":2091,"color":2092},"components","05B979",{"name":2094,"color":2095},"❗ p4-important","D93F0B",13538,"Autoimport components dir","2023-10-06T09:49:35Z","https://github.com/nuxt/nuxt/issues/13538",0.6392559,{"description":2102,"labels":2103,"number":2108,"owner":1991,"repository":1991,"state":2013,"title":2109,"updated_at":2110,"url":2111,"score":2112},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.1\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.4\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-jldudq?file=modules%2Fregister-component.js\r\n\r\n### Describe the bug\r\n\r\nI'm importing the \"@tabler/icons-vue\" library and I want to globally register some of the icons so I can show them using as dynamic components via `\u003Ccomponent :is=\"a\" />`\r\n\r\nIf global is set to false everything works as expected and i can render the component using it's name.\r\nSetting global to true throws this error:\r\n\r\n`Uncaught SyntaxError: The requested module '/_nuxt/node_modules/@tabler/icons-vue/dist/esm/tabler-icons-vue.mjs?nuxt_component=async&nuxt_component_name=IconAnalyze' does not provide an export named 'IconAnalyze' (at components.plugin.mjs:1:10)`\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_",[2104,2105,2106,2107],{"name":2004,"color":2005},{"name":2007,"color":2008},{"name":2091,"color":2092},{"name":2076,"color":2077},26471,"@nuxt/kit.addComponent fails when using external npm package + global = true","2024-04-03T09:15:37Z","https://github.com/nuxt/nuxt/issues/26471",0.64061797,["Reactive",2114],{},["Set"],["ShallowReactive",2117],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"O0cId0_DuFJim7MNe1EDcwRj6xvdf_CSv4pqkruFoD8":-1},"/nuxt/nuxt/12962"]