\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3187,3188,3191],{"name":3146,"color":3147},{"name":3189,"color":3190},"v3","49DCB8",{"name":3192,"color":3193},"triage","ffffff",4407,"ui","SelectInput search-input props has typescript errors with native input attributes","2025-07-12T12:31:08Z","https://github.com/nuxt/ui/issues/4407",0.65044,{"description":3201,"labels":3202,"number":3213,"owner":3152,"repository":3152,"state":3153,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Environment\n\n```\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.1\n- Nuxt Version: 4.1.0\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\n- 4.1.0 https://codesandbox.io/p/devbox/defineemit-types-with-nuxt-4-1-0-3xlf5l (`npx nuxt typecheck` Fails)\n- 4.0.3 https://codesandbox.io/p/devbox/funny-darkness-rs5n63 (`npx nuxt typecheck` Passes)\n\n### Describe the bug\n\nUpgrading from 4.0.3 to 4.1.0 and my `defineEmits` types are not getting registered properly.\n\nExample:\n\nIn child component\n```ts\nconst emit = defineEmits\u003C{\n (e: \"myevent\", value: boolean): void;\n}>();\n```\n\nIn parent component\n```vue\n\u003CMyButton @myevent=\"(v) => console.log(v)\" />\n```\n\nOn 4.0.3, `npx nuxt typecheck` works fine. On 4.1.0, I get `error TS7006: Parameter 'v' implicitly has an 'any' type.`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3203,3204,3207,3210],{"name":3173,"color":3174},{"name":3205,"color":3206},"✨ good reproduction","fbca04",{"name":3208,"color":3209},"4.x","3B01A5",{"name":3211,"color":3212},"possible regression","B90A42",33142,"defineEmits types not being registered","2025-09-05T08:30:05Z","https://github.com/nuxt/nuxt/issues/33142",0.65145373,{"labels":3219,"number":3222,"owner":3152,"repository":3152,"state":3153,"title":3223,"updated_at":3224,"url":3225,"score":3226},[3220,3221],{"name":3143,"color":3144},{"name":3163,"color":3164},13714,"Types for defineNuxtPlugin and nuxtApp","2024-10-29T00:10:15Z","https://github.com/nuxt/nuxt/issues/13714",0.6517274,{"description":3228,"labels":3229,"number":3232,"owner":3152,"repository":3152,"state":3153,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Versions\r\n\r\n- nuxt: 2.15.3\r\n- node: v14.16.0\r\n\r\n### Reproduction\r\n\r\nI set up a fresh installation of Nuxt today for a project. I use the above mentioned version with Typescript.\r\n\r\nThen I created the component below and created a constant there in the data() method using a constant declaration and also assigned a type to it, as well as returned it via the return object. \r\n\r\nWhen running `npm run dev` I got the following error message, which I can't understand. Because I wrote the same thing in another project with an older Nuxt version and it could be executed.\r\n\r\n```bash\r\n✔ Builder initialized 21:42:22\r\n✔ Nuxt files generated 21:42:22\r\n\r\n✖ Client\r\n Compiled with some errors in 5.93s\r\n\r\n\r\n ERROR Failed to compile with 1 errors friendly-errors 21:42:29\r\n\r\n\r\n ERROR in ./components/form.vue?vue&type=script&lang=ts& friendly-errors 21:42:29\r\n\r\nModule parse failed: Unexpected token (29:17) friendly-errors 21:42:29\r\nFile was processed with these loaders:\r\n * ./node_modules/vue-loader/lib/index.js\r\nYou may need an additional loader to handle the result of these loaders.\r\n| export default Vue.extend({\r\n| data() {\r\n> const taxable: Taxable | null = null\r\n| \r\n| return {\r\n friendly-errors 21:42:29\r\n @ ./components/form.vue?vue&type=script&lang=ts& 1:0-116 1:132-135 1:137-250 1:137-250\r\n @ ./components/form.vue\r\n @ ./.nuxt/components/plugin.js\r\n @ ./.nuxt/index.js\r\n @ ./.nuxt/client.js\r\n @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js\r\n friendly-errors 21:42:29\r\nℹ Waiting for file changes 21:42:29\r\nℹ Memory usage: 201 MB (RSS: 317 MB) 21:42:29\r\nℹ Listening on: http://localhost:3000/ 21:42:29\r\n```\r\n\r\n\r\n### Steps to reproduce\r\nI have created this SFC.\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Csection class=\"relative w-full h-auto py-8\">\r\n \u003C!-- some html stuff - not interested! -->\r\n \u003C/section>\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\">\r\nimport Vue from 'vue'\r\nimport { Taxable } from '~/interfaces/index' // return a valid typescript interface\r\n\r\nexport default Vue.extend({\r\n data() {\r\n const taxable: Taxable | null = null\r\n\r\n return {\r\n taxable,\r\n }\r\n }\r\n})\r\n\u003C/script>\r\n\r\n\u003Cstyle lang=\"scss\">\r\n// some styling\r\n\u003C/style>\r\n```\r\n\r\n### What is Expected?\r\nI expect this to compile correctly and launch the app.\r\n\r\n### What is actually happening?\r\nBuild aborts.",[3230,3231],{"name":3163,"color":3164},{"name":3177,"color":3178},9047,"Nuxt build aborts on const declaration in data() - Typescript","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/9047",0.65199214,{"description":3238,"labels":3239,"number":3245,"owner":3152,"repository":3152,"state":3153,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.1`\r\n- Nuxt Version: `3.3.2`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://github.com/niklv/nuxt-component-props-def-bug\n\n### Describe the bug\n\nFor my project config typing I need to refer to typing of component props.\r\nI try extract props typing in this way. But looks like there are no props typing at all.\r\n```vue\r\n\u003Cscript lang=\"ts\" setup>\r\n// ComponentA.vue\r\nconst {propA} = defineProps\u003C{\r\n propA: string\r\n}>()\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv v-text=\"propA\" />\r\n\u003C/template>\r\n\r\n```\r\n\r\n```ts\r\n// config.ts\r\nimport type {ComponentA} from \"#components\";\r\nimport {ComponentOptionsBase} from \"@vue/runtime-core\";\r\n\r\n\r\ntype ComponentProps\u003CT> = T extends ComponentOptionsBase\u003Cinfer P, // Props\r\n any, // RawBindings\r\n any, // D\r\n any, // C\r\n any, // M\r\n any, // Mixin\r\n any, // Extends\r\n any> ? unknown extends P ? {} : P : {};\r\n\r\n\r\ntype CompAProps = ComponentProps\u003Ctypeof ComponentA>\r\n\r\n\r\nconst someConfig:CompAProps = {\r\n // @ts-expect-error\r\n notExistedProp: true // should be error\r\n}\r\n```\n\n### Additional context\n\n\r\n\r\nThere are must be some props typing in first generic argument of `DefineComponent`\n\n### Logs\n\n_No response_",[3240,3241,3242],{"name":3173,"color":3174},{"name":3143,"color":3144},{"name":3243,"color":3244},"upstream","E8A36D",20010,"Empty global components props typings","2023-10-22T09:01:34Z","https://github.com/nuxt/nuxt/issues/20010",0.65427464,{"description":3251,"labels":3252,"number":3255,"owner":3152,"repository":3152,"state":3153,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.19.1`\r\n- Nuxt Version: `0.0.0`\r\n- Nitro Version: `-`\r\n- Package Manager: `unknown`\r\n- Builder: `webpack`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\n\n### Reproduction\n\nCopy paste the `modules` from the Nuxt Documentation.\r\n\r\n```\r\nimport { defineNuxtConfig } from 'nuxt/config';\r\n\r\nexport default defineNuxtConfig({\r\n modules: [\r\n // Using package name\r\n '@nuxtjs/axios',\r\n // Relative to your project srcDir\r\n '~/modules/awesome.js',\r\n // Providing options\r\n ['@nuxtjs/google-analytics', { ua: 'X1234567' }],\r\n // Inline definition\r\n function () {},\r\n ],\r\n});\r\n```\n\n### Describe the bug\n\nThis started to happen when I updated from nuxt 3.3.0 to 3.4.2.\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3253,3254],{"name":3143,"color":3144},{"name":3163,"color":3164},20524,"TS2589: Type instantiation is excessively deep and possibly infinite","2023-10-02T12:08:20Z","https://github.com/nuxt/nuxt/issues/20524",0.65431195,{"description":3261,"labels":3262,"number":3265,"owner":3152,"repository":3195,"state":3153,"title":3266,"updated_at":3267,"url":3268,"score":3269},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[3263,3264],{"name":3146,"color":3147},{"name":3189,"color":3190},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.65447587,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fvVU26cf1P5qGUwo3u6iFpgwBjdm9HmdkJLv3mUAfFsQ":-1},"/nuxt/ui/4959"]