\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_",[2051,2052,2053,2054],{"name":2027,"color":2028},{"name":2001,"color":2002},{"name":2040,"color":2041},{"name":2055,"color":2056},"upstream","E8A36D",21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6559149,{"description":2063,"labels":2064,"number":2070,"owner":1990,"repository":1990,"state":1991,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### What problem does this feature solve?\r\n\r\nThis will allow us to have better DX when developing application with Nuxt.js and be able to use these file extensions.\r\n\r\nCurrently Nuxt pages only pick up .js/.vue files.\r\n\r\n### What does the proposed changes look like?\r\n\r\nSince Nuxt.js `2.0` is already using Babel 7. I currently manage to use Typescript by just adding `@babel/preset-typescript` and a few other babel plugins.\r\n\r\n**But** Nuxt only pick up pages with .js/.vue files.\r\n\r\n```vue\r\n\u003Cscript lang=\"ts\">\r\n// this works by adding those typescript preset & plugins\r\n\u003Cscript>\r\n```\r\n\r\nNuxt.js needs to allow pages with .ts/.tsx also.\r\n\r\n\u003C!--cmty-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8168\">#c8168\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2065,2066,2069],{"name":1984,"color":1985},{"name":2067,"color":2068},"good first issue","fbca04",{"name":1987,"color":1988},4361,"feat: honor .ts/.tsx pages","2023-02-06T11:25:14Z","https://github.com/nuxt/nuxt/issues/4361",0.6600859,{"labels":2076,"number":2079,"owner":1990,"repository":1990,"state":1991,"title":2080,"updated_at":2081,"url":2082,"score":2083},[2077,2078],{"name":1984,"color":1985},{"name":2001,"color":2002},12962,"Type Support for Global Components (e.g. `\u003Cnuxt-link>`)","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12962",0.66287863,{"labels":2085,"number":2088,"owner":1990,"repository":1990,"state":1991,"title":2089,"updated_at":2090,"url":2091,"score":2092},[2086,2087],{"name":2001,"color":2002},{"name":2004,"color":2005},11911,"type augmentation issues","2023-01-19T15:49:25Z","https://github.com/nuxt/nuxt/issues/11911",0.66336566,{"description":2094,"labels":2095,"number":2106,"owner":1990,"repository":1990,"state":1991,"title":2107,"updated_at":2108,"url":2109,"score":2110},"### Environment\n\n```\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `typescript`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-lbhhuu?file=app.vue\r\n\r\n(Since this issue is related to autocomplete behavior, I originally reproduced it in VS Code)\n\n### Describe the bug\n\n`\u003CNuxtPage>`'s props does not appear to be detectable by IDEs such as VS Code. For example, [pageKey](https://nuxt.com/docs/api/components/nuxt-page#example) is valid prop for `\u003CNuxtPage>` but does not show up under completion menu.\r\n\r\n\r\n\n\n### Additional context\n\nI've tried switching between Volar's Take Over Mode and TypeScript Vue Plugin, along with re-enabling the shim in `nuxt.config.ts`, but could not resolve this issue.\n\n### Logs\n\n_No response_",[2096,2097,2098,2099,2102,2103],{"name":2067,"color":2068},{"name":2027,"color":2028},{"name":2001,"color":2002},{"name":2100,"color":2101},"dx","C39D69",{"name":2004,"color":2005},{"name":2104,"color":2105},"馃敤 p3-minor","FBCA04",12395,"Prop completion does not work for `\u003CNuxtPage>`","2023-01-25T08:45:01Z","https://github.com/nuxt/nuxt/issues/12395",0.6654454,["Reactive",2112],{},["Set"],["ShallowReactive",2115],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"A9KaErZi_eOm73bTdJGozYCcpIrc8gUaiS43PcTtGcg":-1},"/nuxt/nuxt/4050"]