",[3020],{"name":3021,"color":3022},"pending triage","E99695",32714,"nuxt","open","fix(types): v4 auto-import in shared directory","2025-07-21T23:23:54Z","https://github.com/nuxt/nuxt/issues/32714",0.6549927,{"description":3031,"labels":3032,"number":3043,"owner":3024,"repository":3024,"state":3044,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.3\r\n- CLI Version: 3.8.3\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: typescript\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nNuxt 3.7.2- works\r\nhttps://stackblitz.com/edit/github-ajlxyx-zupgpe?file=package.json,index.d.ts\r\n\r\nNuxt 3.7.3 - doesn't work\r\nhttps://stackblitz.com/edit/github-ajlxyx?file=app.config.ts,app.vue,package.json\r\n\r\n### Describe the bug\r\n\r\nTry to run `npx nuxi typecheck`. `useAppConfig()` doesn't get types from `index.d.ts` in Nuxt 3.7.3.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3033,3036,3037,3040],{"name":3034,"color":3035},"types","2875C3",{"name":3021,"color":3022},{"name":3038,"color":3039},"🔨 p3-minor","FBCA04",{"name":3041,"color":3042},"possible regression","B90A42",23207,"closed","Manually typing App Config doesn't work","2025-05-29T21:32:27Z","https://github.com/nuxt/nuxt/issues/23207",0.6246043,{"labels":3050,"number":3059,"owner":3024,"repository":3024,"state":3044,"title":3060,"updated_at":3061,"url":3062,"score":3063},[3051,3052,3055,3058],{"name":3034,"color":3035},{"name":3053,"color":3054},"3.x","29bc7f",{"name":3056,"color":3057},"bug","d73a4a",{"name":3038,"color":3039},13713,"`#imports` types don't include server auto-imports","2023-03-13T16:54:30Z","https://github.com/nuxt/nuxt/issues/13713",0.63479245,{"description":3065,"labels":3066,"number":3071,"owner":3024,"repository":3024,"state":3044,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### Environment\n\nNuxi 3.3.1 17:37:15\r\n 17:37:16\r\nRootDir: /Users/Shared/git/nuxt3.3-breaking 17:37:16\r\nNuxt project info: (copied to clipboard) 17:37:16\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.3.1`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `srcDir`, `build`, `css`, `components`, `nitro`, `vite`, `modules`, `alias`, `typescript`, `experimental`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nminimal reproduce repo:\r\nhttps://github.com/arily/nuxt3.3-breaking\r\n\r\nI included the generated .nuxt folder to make sure if platform difference is to blame.\n\n### Describe the bug\n\n\r\n\r\nAppConfig lost its type in 3.3.0 (and after).\r\n\r\n\r\nsame code in nuxt 3.2.3\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3067,3068,3069,3070],{"name":3034,"color":3035},{"name":3053,"color":3054},{"name":3056,"color":3057},{"name":3038,"color":3039},20103,"nuxt3.3.0 breaks AppConfig","2023-04-06T12:33:55Z","https://github.com/nuxt/nuxt/issues/20103",0.6447907,{"description":3077,"labels":3078,"number":3086,"owner":3024,"repository":3024,"state":3044,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.5.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@10.2.3`\r\n- Builder: `-`\r\n- User Config: `devtools`, `build`, `modules`, `vite`\r\n- Runtime Modules: `()`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nuse the code from the documentation: https://nuxt.com/docs/api/utils/define-nuxt-component#head\r\n\r\n### Describe the bug\r\n\r\nAs shown in the documentation: https://nuxt.com/docs/api/utils/define-nuxt-component#head\r\n\r\nUsing that code (`head(nuxtApp) {}`), then `nuxtApp` has no type, implicitly \"any\".\r\n\r\n\u003Cimg width=\"769\" alt=\"Bildschirmfoto 2023-12-18 um 14 35 42\" src=\"https://github.com/nuxt/nuxt/assets/1894723/f05cfb43-b610-4db7-885e-9ccfdad099f9\">\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3079,3082,3083,3084,3085],{"name":3080,"color":3081},"good first issue","fbca04",{"name":3034,"color":3035},{"name":3053,"color":3054},{"name":3056,"color":3057},{"name":3038,"color":3039},24811,"Type missing: for `head(nuxtApp) {}`","2024-02-22T11:11:45Z","https://github.com/nuxt/nuxt/issues/24811",0.6529659,{"description":3092,"labels":3093,"number":3100,"owner":3024,"repository":3024,"state":3044,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `modules`, `i18n`\r\n- Runtime Modules: `@nuxtjs/i18n@8.0.0-beta.9`, `@nuxtjs/apollo@5.0.0-alpha.5`, `@pinia/nuxt`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ly14ux?file=nuxt.config.ts,package.json,README.md\n\n### Describe the bug\n\n- Installing this 3 modules seem to trigger the bug, could be one individually (i18n, apollo, pinia)\r\n- defineNuxtConfig when we add, for example, i18n options says that those options don't exist inside the NuxtConfig type.\r\n\n\n### Additional context\n\nhttps://discord.com/channels/473401852243869706/1077187385667899422\n\n### Logs\n\n```shell-script\nArgument of type '{ modules: string[]; i18n: { noTypescriptWorkingHere: string; }; }' is not assignable to parameter of type 'NuxtConfig'.\r\n Object literal may only specify known properties, and 'i18n' does not exist in type 'NuxtConfig'.(2345)\n```\n",[3094,3095,3096,3097],{"name":3034,"color":3035},{"name":3053,"color":3054},{"name":3056,"color":3057},{"name":3098,"color":3099},"❗ p4-important","D93F0B",19214,"NuxtConfig typescript not detecting modules options","2024-07-21T13:01:37Z","https://github.com/nuxt/nuxt/issues/19214",0.6530321,{"description":3106,"labels":3107,"number":3112,"owner":3024,"repository":3024,"state":3044,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-2l517b\r\n\r\n```\r\n$ npm i\r\n$ npm run typecheck\r\n```\r\n\n\n### Describe the bug\n\n\r\nThe code below gives an error.\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>index\u003C/h1>\r\n \u003Cp>{{ $config.public.flag }}\u003C/p>\u003C!-- type error -->\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n\r\n```vue\r\n\u003Cscript lang=\"ts\">\r\nexport default defineNuxtComponent({\r\n created() {\r\n console.log(this.$config.public.flag); // type error\r\n },\r\n});\r\n\u003C/script>\r\n```\r\n\r\nI paste the log when type checking at the bottom.\r\n\r\nThis is a problem that occurs from v3.3.3.\r\nIt did not occur with v3.2.3. (https://stackblitz.com/edit/github-2l517b-cwvb5p)\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n❯ npm run typecheck\r\n$ nuxt typecheck\r\nNuxi 3.3.3 16:52:14\r\npages/index.vue:4:11 - error TS2339: Property '$config' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial\u003C{}> & Omit\u003CReadonly\u003CExtractPropTypes\u003C{}>> & VNodeProps & AllowedComponentProps & ComponentCustomProps, never>; ... 10 more ...; $watch\u003CT extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => ...'.\r\n\r\n4 \u003Cp>{{ $config.public.flag }}\u003C/p>\r\n ~~~~~~~\r\n\r\npages/option.vue:4:22 - error TS2339: Property '$config' does not exist on type 'CreateComponentPublicInstance\u003C{}, {}, {}, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, {}, {}, {}, false, {}, OptionTypesType\u003C{}, {}, {}, {}, {}, {}>, ... 5 more ..., {}>'.\r\n\r\n4 console.log(this.$config.public.flag);\r\n ~~~~~~~\r\n\r\npages/option.vue:12:11 - error TS2339: Property '$config' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial\u003C{}> & Omit\u003CReadonly\u003CExtractPropTypes\u003C{}>> & VNodeProps & AllowedComponentProps & ComponentCustomProps, never>; ... 10 more ...; $watch\u003CT extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => ...'.\r\n\r\n12 \u003Cp>{{ $config.public.flag }}\u003C/p>\r\n ~~~~~~~\r\n\r\n\r\nFound 3 errors in 2 files.\r\n\r\nErrors Files\r\n 1 pages/index.vue:4\r\n 2 pages/option.vue:4\r\n\r\n ERROR Command failed with exit code 2: vue-tsc --noEmit 16:52:17\r\n\r\n at makeError (file://node_modules/nuxi/dist/shared/nuxi.63bda57d.mjs:640:11)\r\n at handlePromise (file://node_modules/nuxi/dist/shared/nuxi.63bda57d.mjs:1129:26)\r\n at async Object.invoke (file://node_modules/nuxi/dist/chunks/typecheck.mjs:69:7)\r\n at async _main (file://node_modules/nuxi/dist/cli.mjs:64:20)\n```\n",[3108,3109,3110,3111],{"name":3034,"color":3035},{"name":3053,"color":3054},{"name":3056,"color":3057},{"name":3038,"color":3039},20069,"`$config` type error","2023-04-04T13:34:42Z","https://github.com/nuxt/nuxt/issues/20069",0.65753055,{"description":3118,"labels":3119,"number":3125,"owner":3024,"repository":3024,"state":3044,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### 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_",[3120,3121,3122,3123],{"name":3034,"color":3035},{"name":3056,"color":3057},{"name":3038,"color":3039},{"name":3124,"color":3081},"✨ good reproduction",28781,"(tsx) Auto imports typings","2024-09-02T11:02:48Z","https://github.com/nuxt/nuxt/issues/28781",0.6584168,{"description":3131,"labels":3132,"number":3134,"owner":3024,"repository":3024,"state":3044,"title":3135,"updated_at":3136,"url":3137,"score":3138},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: -\r\n- Package Manager: pnpm@8.15.3\r\n- Builder: -\r\n- User Config: devtools, modules, ui, colorMode\r\n- Runtime Modules: @nuxt/ui@2.15.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-yurofm?file=package.json,nuxt.config.ts\n\n### Describe the bug\n\nWhen using a module, for example `@nuxt/ui`, and installing dependencies with `pnpm`, the extended type for NuxtConfig is not being picked up by Typescript (both `tsc` and `vue-tsc`). This leads to a type error in `nuxt.config.ts`: \r\n```\r\nnuxt.config.ts:5:3 - error TS2353: Object literal may only specify known properties, and 'ui' does not exist in type 'InputConfig\u003CNuxtConfig, ConfigLayerMeta>'.\r\n\r\n5 ui: {\r\n ~~\r\n\r\nFound 1 error in nuxt.config.ts:5\r\n```\r\n\r\nAdditionally, I found that:\r\n- the extended interface is present in `.nuxt/schema.d.ts`\r\n- removing `node_modules` and reinstalling with `npm` will fix the error\r\n- type casting the input parameter of `defineNuxtConfig` as `InputConfig\u003CNuxtConfig>` will circumvent the issue, but requires me to add `c12` as a dependency\n\n### Additional context\n\nThis is my first project using `pnpm`, but I decided to give it a go after I saw `nuxt` itself uses it. Because of that I was also surprised I did not find any other issues mentioning this. So perhaps this is a misconfiguration on my end, and people here know the answer straight away. But I decided to open a bug since I could easily reproduce the issue with Stackblitz.\n\n### Logs\n\n_No response_",[3133],{"name":3021,"color":3022},26921,"Typescript not picking up extended NuxtConfig interface when installing with pnpm","2024-09-04T14:52:29Z","https://github.com/nuxt/nuxt/issues/26921",0.6591069,{"labels":3140,"number":3149,"owner":3024,"repository":3024,"state":3044,"title":3150,"updated_at":3151,"url":3152,"score":3153},[3141,3142,3143,3146],{"name":3053,"color":3054},{"name":3056,"color":3057},{"name":3144,"color":3145},"nitro","bfd4f2",{"name":3147,"color":3148},"schema","1d76db",12899,"`NuxtConfig` missing `nitro` type ","2023-01-19T16:43:29Z","https://github.com/nuxt/nuxt/issues/12899",0.660446,["Reactive",3155],{},["Set"],["ShallowReactive",3158],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faY9xSZzBTU38sxMMSHPbNRS71NcM17ZpUBaSu06wA18":-1},"/nuxt/nuxt/25918"]