\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_",[3206,3207,3208,3209],{"name":3142,"color":3143},{"name":3145,"color":3146},{"name":3179,"color":3180},{"name":3210,"color":3211},"upstream","E8A36D",21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6525072,{"description":3218,"labels":3219,"number":3222,"owner":3151,"repository":3151,"state":3152,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n- Node Version: v19.4.0\r\n- Nuxt Version: 3.7.4\r\n\n\n### Reproduction\n\nReproduced with nuxt starter v3 codesandbox (with `experimental.typedPages` enabled)\r\n\r\nhttps://github.com/nuxt/starter/tree/v3-codesandbox\n\n### Describe the bug\n\nWith the `typedPages` feature enabled :\r\n\r\n```js\r\nexperimental: {\r\n typedPages: true\r\n},\r\n```\r\n\r\nOn Intellij IDE (WebStorm/PHPStorm), code suggestions (autocompletion)(Ctrl+Space) doesn't work when using `NuxtLink` component, on the template block (same issue with VSCode)\r\n\r\nIt works fine with composable `useRouter` and `useRoute`, I can retrieve the correct type and visualize the routes of my application.\r\n\r\nAccording to the README of the [unplugin-vue-router](https://github.com/posva/unplugin-vue-router), code suggestions on VSCode seems possible.\r\n\r\nThe `vue-tsc` tool work as intended on `NuxtLink` and can detect typescript errors. I guess the types of vue-router is correctly generated.\r\n\r\nAm I missing something ?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3220,3221],{"name":3145,"color":3146},{"name":3179,"color":3180},23618,"Code suggestions with typedPages enabled doesn't work on IntelliJ / VSCode","2023-10-11T14:26:10Z","https://github.com/nuxt/nuxt/issues/23618",0.65861964,{"labels":3228,"number":3230,"owner":3151,"repository":3151,"state":3152,"title":3231,"updated_at":3232,"url":3233,"score":3234},[3229],{"name":3148,"color":3149},4134,"TS2314: Generic type 'ComponentOptions\u003CV>' requires 1 type argument(s).","2023-01-18T20:03:58Z","https://github.com/nuxt/nuxt/issues/4134",0.6593162,{"description":3236,"labels":3237,"number":3250,"owner":3151,"repository":3151,"state":3152,"title":3251,"updated_at":3252,"url":3253,"score":3254},"### 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_",[3238,3241,3242,3243,3246,3247],{"name":3239,"color":3240},"good first issue","fbca04",{"name":3142,"color":3143},{"name":3145,"color":3146},{"name":3244,"color":3245},"dx","C39D69",{"name":3193,"color":3194},{"name":3248,"color":3249},"🔨 p3-minor","FBCA04",12395,"Prop completion does not work for `\u003CNuxtPage>`","2023-01-25T08:45:01Z","https://github.com/nuxt/nuxt/issues/12395",0.6639975,{"labels":3256,"number":3259,"owner":3151,"repository":3151,"state":3152,"title":3260,"updated_at":3261,"url":3262,"score":3263},[3257,3258],{"name":3179,"color":3180},{"name":3148,"color":3149},6894,"Typescript linting issue","2023-01-22T15:34:48Z","https://github.com/nuxt/nuxt/issues/6894",0.6639989,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fA9KaErZi_eOm73bTdJGozYCcpIrc8gUaiS43PcTtGcg":-1},"/nuxt/nuxt/4050"]