\n\nWhere I use config then, it shows me typing error.\nWhen I switch to the legacy tsconfig, typing issue are gone.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nTypecheck summary: \n\n\n\napp/layouts/default.vue:35:33 - error TS2339: Property 'title' does not exist on type '{}'.\n\n35 title: appConfig.information?.title,\n ~~~~~\n\napp/layouts/default.vue:36:39 - error TS2339: Property 'description' does not exist on type '{}'.\n\n36 description: appConfig.information?.description,\n ~~~~~~~~~~~\n\napp/layouts/default.vue:39:36 - error TS2339: Property 'socials' does not exist on type '{}'.\n\n39 github: appConfig.information?.socials?.github,\n ~~~~~~~\n\napp/layouts/default.vue:40:38 - error TS2339: Property 'socials' does not exist on type '{}'.\n\n40 linkedin: appConfig.information?.socials?.linkedin,\n ~~~~~~~\n\napp/layouts/default.vue:41:40 - error TS2339: Property 'birthdate' does not exist on type '{}'.\n\n41 isBirthday: appConfig.information?.birthdate ? isBirthday(appConfig.information?.birthdate) : false,\n ~~~~~~~~~\n\napp/layouts/default.vue:41:86 - error TS2339: Property 'birthdate' does not exist on type '{}'.\n\n41 isBirthday: appConfig.information?.birthdate ? isBirthday(appConfig.information?.birthdate) : false,\n ~~~~~~~~~\n\napp/layouts/default.vue:44:27 - error TS2339: Property 'icons' does not exist on type '{}'.\n\n44 normal: appConfig.ui?.icons?.normal as string[] ?? [],\n ~~~~~\n\napp/layouts/default.vue:45:29 - error TS2339: Property 'icons' does not exist on type '{}'.\n\n45 birthday: appConfig.ui?.icons?.birthday as string[] ?? [],\n ~~~~~\n\napp/middleware/title.global.ts:5:28 - error TS2571: Object is of type 'unknown'.\n\n5 const appConfigTitle = useAppConfig().information.title;\n ~~~~~~~~~~~~~~~~~~~~~~~~~~\n\napp/pages/index.vue:14:62 - error TS2339: Property 'messages' does not exist on type '{}'.\n\n14 const messages = useState('randomIndex', () => appConfig.ui?.messages?.sort(() => Math.random() - 0.5))\n ~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n```",[3137,3140],{"name":3138,"color":3139},"pending triage","E99695",{"name":3141,"color":3142},"possible regression","B90A42",32768,"nuxt","open","useAppConfig lose types from nuxt schema with new tsconfig","2025-07-25T22:51:01Z","https://github.com/nuxt/nuxt/issues/32768",0.6343714,{"description":3151,"labels":3152,"number":3154,"owner":3144,"repository":3144,"state":3145,"title":3155,"updated_at":3156,"url":3157,"score":3158},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-ki8poq\r\n> Run \"pnpm frontend typecheck\" to see it broken in action\r\n\r\n### Describe the bug\r\n\r\nIf nuxt is installed as a monorepo project, and there is a tsconfig.json in the package's root, with the below contents, component props are failing to be parsed properly, breaking both intellisense and vue-tsc:\r\n```json\r\n{\r\n \"extends\": \"./.nuxt/tsconfig.json\"\r\n}\r\n```\r\n\r\n### Additional context\r\n\r\nI'm not 100% sure if this is a language tools bug or a nuxt bug, but since the problem seemingly occurs *upon* extending nuxt's autogenerated tsconfig, I figured I'd first raise an issue here first so that, if it is actually a language tools bug, we can give more detailed context to them.\r\n\r\n### Logs\r\n\r\n_No response_",[3153],{"name":3138,"color":3139},28431,"vue-tsc is broken if there exists a tsconfig.json that extends nuxt's generated tsconfig when nuxt is in a monorepo project","2024-10-16T08:15:01Z","https://github.com/nuxt/nuxt/issues/28431",0.65700835,{"description":3160,"labels":3161,"number":3162,"owner":3144,"repository":3163,"state":3164,"title":3165,"updated_at":3166,"url":3167,"score":3168},"##error message\r\n\r\n ERROR(vue-tsc) Property 'nuxtIcon' does not exist on type 'AppConfig'.\r\nconst props = defineProps({\r\n name: {\r\n type: String as PropType\u003Ckeyof AppConfig['nuxtIcon']['aliases'] | (string & {})>,\r\n ^^^^^^^^^^\r\n required: true\r\n },\r\n\r\n##code\r\n\r\n```ts\r\n\r\nexport default defineNuxtConfig({\r\n srcDir: 'src',\r\n ssr: false,\r\n typescript: {\r\n typeCheck: true\r\n },\r\n modules: ['@nuxtjs/tailwindcss', 'nuxt-icon']\r\n\r\n})\r\n```",[],46,"icon","closed","Error something on nuxt 3.1.0 - ERROR(vue-tsc) Property 'nuxtIcon' does not exist on type 'AppConfig'.","2023-01-27T14:11:31Z","https://github.com/nuxt/icon/issues/46",0.6095291,{"description":3170,"labels":3171,"number":3184,"owner":3144,"repository":3144,"state":3164,"title":3185,"updated_at":3186,"url":3187,"score":3188},"### 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",[3172,3175,3178,3181],{"name":3173,"color":3174},"types","2875C3",{"name":3176,"color":3177},"3.x","29bc7f",{"name":3179,"color":3180},"bug","d73a4a",{"name":3182,"color":3183},"🔨 p3-minor","FBCA04",20069,"`$config` type error","2023-04-04T13:34:42Z","https://github.com/nuxt/nuxt/issues/20069",0.61438125,{"description":3190,"labels":3191,"number":3198,"owner":3144,"repository":3144,"state":3164,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-njy44nnk\n\n### Describe the bug\n\nIn the Nuxt config file, the expected type for the `typescript.tsConfig.vueCompilerOptions.plugins` key is `(VueLanguagePlugin | undefined)[] | undefined` (from `@vue/language-core` via `@nuxt/schema`). However, if you follow the type and provide it a `VueLanguagePlugin`, the generated `tsconfig` in `.nuxt` would be `null` instead of the plugin name in the `vueCompilerOptions.plugins` key.\n\nThe reproduction uses `@vue/language-plugin-pug`; instead of seeing `@vue/language-plugin-pug` in `vueCompilerOptions.plugins` in the generated `tsconfig`, we see `null` instead.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3192,3195,3196,3197],{"name":3193,"color":3194},"good first issue","fbca04",{"name":3173,"color":3174},{"name":3179,"color":3180},{"name":3182,"color":3183},30432,"Incorrect `vueCompilerOptions.plugins` in `tsconfig` when generated from `nuxt.config`","2025-01-04T22:30:03Z","https://github.com/nuxt/nuxt/issues/30432",0.6182588,{"description":3204,"labels":3205,"number":3210,"owner":3144,"repository":3144,"state":3164,"title":3211,"updated_at":3212,"url":3213,"score":3214},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.14.12\r\n\r\n### Reproduction\r\nCreating nuxt.config.ts (typescripted file) with '@nuxt/types' NuxtConfig type and using vue.config property to change vue global configs and only passing one property we get Typescript error, to use them all.\r\n\r\n\r\n### Steps to reproduce\r\nJust add at least one property to nuxt.config.ts -> vue -> config\r\n\r\n### What is Expected?\r\nAllowing to provide any number of properties, and not passing them all.\r\n\r\n### What is actually happening?\r\nTypescript asks to use all properties of the NuxtOptionsVueConfiguration typescript type.\r\n\r\nAnd looking at the docs of nuxt we see:\r\n```\r\nexport default {\r\n vue: {\r\n config: {\r\n productionTip: true,\r\n devtools: false\r\n }\r\n }\r\n}\r\n```\r\n\r\nwhich is impossible to achieve while using the types as we get:\r\n```\r\nType '{ ignoredElements: string[]; }' is missing the following properties from type 'VueConfiguration': silent, optionMergeStrategies, devtools, productionTip, and 5 more.ts(2740)\r\n```\r\n\r\n### Solution\r\nAs I do not have much time right now, but I believe that the options should be Partial\u003CVueConfiguration> and not just VueConfiguration.\r\n\r\n```nuxt.js/packages/types/config/index.d.ts```\r\n\r\n```\r\n router: NuxtOptionsRouter\r\n server: NuxtOptionsServer\r\n serverMiddleware: NuxtOptionsServerMiddleware[]\r\n srcDir: string\r\n transition: Transition\r\n vue: {\r\n config?: NuxtOptionsVueConfiguration \u003C-- this one I believe should be Partial\u003CNuxtOptionsVueConfiguration>\r\n }\r\n watch: string[]\r\n watchers: NuxtOptionsWatchers\r\n}\r\n```",[3206,3207],{"name":3138,"color":3139},{"name":3208,"color":3209},"2.x","d4c5f9",8766,"@nuxt/types vue config have to pass all Vue config properties, otherwise Typescript throws an error","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8766",0.6211162,{"description":3216,"labels":3217,"number":3224,"owner":3144,"repository":3144,"state":3164,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n**VsCode 1.79.2**\r\n- vscode.typescript-language-features: disabled\r\n- Vue.volar: 1.8.3, enabled\r\n- Vue.vscode-typescript-vue-plugin: 1.8.3, enabled\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/niklas-may/nuxt-module-issue-reproduction\r\n\r\n### Describe the bug\r\n\r\n**Preface**\r\n_Thank you for your amazing work on Nuxt! I am not sure where this issue is best raised, Nuxt, VsCode or Vue. But due to the special typescript tooling with auto imports, I thought it's best to start here, and would be happy to hear if anybody observed a similar behaviour or has a solution._ \r\n\r\n**Description**\r\nWhen I open `~/.nuxt/components.d.ts` in VsCode and hover over an imported component, VsCode IntelliSense popover displays the correct types for this component.\r\nBut when I use the component in any other components template block, for example `~/app.vue`, the typing is missing the prop types.\r\n\r\n### Component and Type Definitions\r\n\r\n`~/../src/runtime/MyButton.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv style=\"border: 1px solid pink\">\r\n \u003Cslot />\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_",[3218,3219,3220,3221],{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3138,"color":3139},{"name":3222,"color":3223},"upstream","E8A36D",21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6420996,{"description":3230,"labels":3231,"number":3234,"owner":3144,"repository":3144,"state":3164,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\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-z6juqt?file=components%2FTest.vue\r\n\r\n`npm run typecheck` in terminal\r\n\r\n```\r\ncomponents/Test.vue:8:17 - error TS2339: Property 'optionalStr' does not exist on type 'CreateComponentPublicInstanceWithMixins\u003CToResolvedProps\u003C{}, {}>, {}, {}, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, {}, VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly\u003C...> & Readonly\u003C...>, ... 16 more ..., {}>'.\r\n\r\n8 \u003Cspan v-if=\"optionalStr\">{{ optionalStr }}\u003C/span>\r\n ~~~~~~~~~~~\r\n```\n\n### Describe the bug\n\nAfter upgrading from Nuxt 3.12.3 to 3.13.2, these TS errors showed up in every component that only uses optional props. The error disappears if we add a single required prop or enable TS strict mode.\n\n### Additional context\n\nThe issue doesn't seem to be present in a pure Vue/Vite project:\r\n\r\nhttps://stackblitz.com/edit/vitejs-vite-ece16d?file=src%2Fcomponents%2FHelloWorld.vue\n\n### Logs\n\n_No response_",[3232,3233],{"name":3138,"color":3139},{"name":3141,"color":3142},29041,"Components with only optional props lose props type if strict mode is disabled","2024-09-23T10:12:23Z","https://github.com/nuxt/nuxt/issues/29041",0.642751,{"description":3240,"labels":3241,"number":3249,"owner":3144,"repository":3144,"state":3164,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, modules, typescript\r\n- Runtime Modules: @nuxtseo/module@2.0.0-beta.15\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n- minimal changes to nuxt config adding `typeCheck: true` and `compilerOptions.noUncheckedIndexedAccess: true`\r\n\r\nhttps://stackblitz.com/edit/github-vdxk2t?file=nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nThis highlights an issue when trying to use tsconfig features e.g. `noUncheckedIndexedAccess` or `noUnusedLocals` etc. in a nuxt project to provide stricter code conformance. Any nuxt module you have installed will also be checked for these same rules.\r\n\r\nThis effectively means you cannot use any of the tsconfig rules for the risk of a module developer not adhering to those same standards.\r\n\r\nNuxt should not be type checking any installed modules as part of build with the same tsconfig rules defined at the project level. Providing access to all tsconfig properties is misleading as they effectively don't work with the nuxt ecosystem unless you have a raw project.\r\n\r\nThe repro and logs below show how this fails for the `@nuxtseo/module` module but this error is present in a number of modules I have tried to use e.g. `content`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nERROR 21:54:09\r\n ERROR(vue-tsc) Type '{ icon: string; label: false; ariaLabel: string | undefined; current?: boolean | undefined; disabled?: boolean | undefined; to?: string | undefined; separator?: string | undefined; hideSeparator?: boolean | undefined; ui?: { ...; } | undefined; }' is not assignable to type 'BreadcrumbItemProps'.\r\n Types of property 'to' are incompatible.\r\n Type 'string | undefined' is not assignable to type 'string'.\r\n Type 'undefined' is not assignable to type 'string'.\r\n FILE /home/projects/github-vdxk2t/node_modules/nuxt-seo-ui/dist/runtime/components/Breadcrumb.vue:46:5\r\n\r\n 44 | }\r\n 45 | if (props.homeIcon) {\r\n > 46 | items[0] = {\r\n | ^^^^^^^^\r\n 47 | ...items[0],\r\n 48 | icon: 'material-symbols:home-outline-rounded',\r\n 49 | label: false,\r\n\r\n[vue-tsc] Found 1 error. Watching for file changes. (x3)\r\n```\r\n```\r\n",[3242,3245,3246,3247,3248],{"name":3243,"color":3244},"discussion","538de2",{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3179,"color":3180},{"name":3182,"color":3183},23609,"`typeCheck` reports errors from modules when using `tsconfig` rules","2023-11-30T07:26:56Z","https://github.com/nuxt/nuxt/issues/23609",0.64350873,{"description":3255,"labels":3256,"number":3257,"owner":3144,"repository":3163,"state":3164,"title":3258,"updated_at":3259,"url":3260,"score":3261},"The same of, but with newer version: \r\nError something on nuxt 3.1.0 - ERROR(vue-tsc) Property 'nuxtIcon' does not exist on type 'AppConfig'. #46 \r\n\r\n\r\n`node_modules/.pnpm/nuxt-icon@0.2.10/node_modules/nuxt-icon/dist/runtime/Icon.vue:34:40`\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.13.0`\r\n- Nuxt Version: `3.1.2`\r\n- Nitro Version: `2.1.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `ssr`, `runtimeConfig`, `app`, `modules`, `directus`, `meilisearch`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.3.1`, `nuxt-directus@3.2.2`, `nuxt-meilisearch@0.1.7`, `nuxt-icon@0.2.10`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\nMy all packages: \r\n```\r\ndependencies:\r\n@nuxtjs/robots 3.0.0 apexcharts 3.37.0 moment 2.29.4 swiper 9.0.3 vue3-apexcharts 1.4.1 \r\n@nuxtjs/tailwindcss 6.3.1 axios 1.3.2 nuxt-directus 3.2.2 type-check 0.4.0 yarn-upgrade-all 0.7.2 \r\n@vueuse/core 9.12.0 daisyui 2.50.0 sanitize-html 2.9.0 vue-instantsearch 4.8.2 \r\n\r\ndevDependencies:\r\n@commitlint/cli 17.4.2 @typescript-eslint/parser 5.51.0 eslint-plugin-prettier 4.2.1 nuxt-icon 0.2.10 \r\n@commitlint/config-conventional 17.4.2 @vue/eslint-config-standard 8.0.1 eslint-plugin-vue 9.9.0 nuxt-meilisearch 0.1.7 \r\n@types/cypress 1.1.3 eslint 8.33.0 husky 8.0.3 prettier 2.8.3 \r\n@types/sanitize-html 2.8.0 eslint-config-prettier 8.6.0 lint-staged 13.1.0 typescript 4.9.5 \r\n@typescript-eslint/eslint-plugin 5.51.0 eslint-plugin-nuxt 4.0.0 nuxt 3.1.2 vue-tsc 1.0.24 \r\n```\r\n",[],50,"error TS2339: Property 'nuxtIcon' does not exist on type 'AppConfig'.","2023-03-15T16:30:19Z","https://github.com/nuxt/icon/issues/50",0.64537555,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fU7LgyjdFw8yg3Gb4dlDqwbPDK0JOvSJjlfYIAotX3T0":-1},"/nuxt/nuxt/25874"]