\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```",[3039,3042],{"name":3040,"color":3041},"pending triage","E99695",{"name":3043,"color":3044},"possible regression","B90A42",32768,"useAppConfig lose types from nuxt schema with new tsconfig","2025-07-25T22:51:01Z","https://github.com/nuxt/nuxt/issues/32768",0.68657887,{"description":3051,"labels":3052,"number":3055,"owner":3029,"repository":3030,"state":3056,"title":3057,"updated_at":3058,"url":3059,"score":3060},"### 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/weathered-resonance-r7wcmc?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nThe carousel item generic type does not seem to work anymore. Unfortunately I'm not sure, which is the last version of nuxt ui where it works :(\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n'item' is possibly 'null'. \nProperty 'title' does not exist on type 'string | number | Record\u003Cstring, any>'.\n Property 'title' does not exist on type 'string'.\n```",[3053,3054],{"name":3020,"color":3021},{"name":3023,"color":3024},4020,"closed","Generic Type Issue with Carousel Component","2025-04-29T15:39:36Z","https://github.com/nuxt/ui/issues/4020",0.6686425,{"description":3062,"labels":3063,"number":3066,"owner":3029,"repository":3030,"state":3056,"title":3067,"updated_at":3068,"url":3069,"score":3070},"\u003Cdetails>\n \u003Csummary>Environment\u003C/summary>\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.4.1\n- Builder: -\n- User Config: modules, ssr, devtools, app, css, ui, runtimeConfig, alias, build, devServer, watch, future, experimental, compatibilityDate, nitro, vite, eslint, heyApi, i18n, icon, svgIconSprite\n- Runtime Modules: @nuxt/ui@3.1.2, @nuxt/test-utils/module@3.19.0, @nuxt/eslint@1.4.1, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.2.0, @hey-api/nuxt@0.1.6, @nuxtjs/i18n@9.5.4, nuxt-svg-icon-sprite@2.0.0\n- Build Modules: -\n------------------------------\n\u003C/details>\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://www.npmjs.com/package/@nuxt/ui?activeTab=code - `interface ModalSlots`\n\n### Description\n\nGreetings, thank you very much for the work you have done!\n\nUsing the example of the `UModal` component, you can see that props in scoped slots, such as `#footer=“{ close }”`, is untyped \n\u003Cdetails>\n \u003Csummary>Example\u003C/summary>\n\n \n\u003C/details>\n\nin the bundle package it can be seen that there are indeed no valid types of props in `ModalSlots` - https://www.npmjs.com/package/@nuxt/ui?activeTab=code `interface ModalSlots`, although they are present in the source files - https://github.com/nuxt/ui/blob/v3/src/runtime/components/Modal.vue#L70\n\n\nAs I understand it, it is not only `UModal`, but all components with scoped slots.",[3064,3065],{"name":3020,"color":3021},{"name":3023,"color":3024},4260,"Scoped slots are not typed","2025-06-02T09:08:41Z","https://github.com/nuxt/ui/issues/4260",0.67184556,{"description":3072,"labels":3073,"number":3077,"owner":3029,"repository":3030,"state":3056,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, piniaPluginPersistedstate, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.3, @pinia/nuxt@0.11.1, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.31.0, @nuxt/scripts@0.11.8, @nuxt/eslint@1.4.1, nuxt-charts@0.1.11, @nuxtjs/mdc@0.17.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nLocal build based on commit 04f12adc5b6124c8371c256d2c40df2be832e6e2\n\n### Reproduction\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nimport type { TimelineItem } from '@nuxt/ui'\nimport { useTimeAgo } from '@vueuse/core'\n\nconst items = [\n {\n username: 'J-Michalek',\n date: '2025-05-24T14:58:55Z',\n action: 'opened this',\n avatar: {\n src: 'https://github.com/J-Michalek.png'\n }\n },\n {\n username: 'J-Michalek',\n date: '2025-05-26T19:30:14+02:00',\n action: 'marked this pull request as ready for review',\n icon: 'i-lucide-check-circle'\n },\n {\n username: 'benjamincanac',\n date: '2025-05-27T11:01:20Z',\n action: 'commented on this',\n description:\n \"I've made a few changes, let me know what you think! Basically I updated the design, removed unnecessary divs, used Avatar component for the indicator since it supports icon already.\",\n avatar: {\n src: 'https://github.com/benjamincanac.png'\n }\n },\n {\n username: 'J-Michalek',\n date: '2025-05-27T11:01:20Z',\n action: 'commented on this',\n description: 'Looks great! Good job on cleaning it up.',\n avatar: {\n src: 'https://github.com/J-Michalek.png'\n }\n },\n {\n username: 'benjamincanac',\n date: '2025-05-27T11:01:20Z',\n action: 'merged this',\n icon: 'i-lucide-git-merge'\n }\n] satisfies TimelineItem[]\n\u003C/script>\n\n\u003Ctemplate> \n \u003CUTimeline\n :items=\"items\"\n size=\"lg\"\n :ui=\"{\n date: 'float-end ms-1',\n description: 'px-3 py-2 ring ring-default mt-2 rounded-md text-default'\n }\"\n >\n \u003Ctemplate #title=\"{ item }\">\n \u003Cspan>{{ item.username }}\u003C/span>\n \u003Cspan class=\"font-normal text-muted\"> {{ item.action }}\u003C/span>\n \u003C/template>\n\n \u003Ctemplate #description=\"{ item }\">\n \n \u003C/template>\n\n \u003Ctemplate #date=\"{ item }\">\n \u003CUTooltip\n v-if=\"item.date\"\n :text=\"new Date(item.date).toLocaleString()\"\n placement=\"bottom-end\"\n >\n \u003Cspan>{{ useTimeAgo(new Date(item.date)) }}\u003C/span>\n \u003C/UTooltip>\n \u003C/template>\n \u003C/UTimeline>\n\u003C/template>\n```\n\n### Description\n\nI'm testing the timeline component for future integration, and I noticed that using slots even if the value is empty and no html is passed it applies the styles.\n\n\n\nI don't know if it's a good solution but something like this can do the trick :\n```vue\n \u003Cdiv v-if=\"item.description || (!!slots.description && item.description)\" :class=\"ui.description({ class: [props.ui?.description, item.ui?.description] })\">\n \u003Cslot :name=\"((item.slot ? `${item.slot}-description` : 'description') as keyof TimelineSlots\u003CT>)\" :item=\"(item as Extract\u003CT, { slot: string; }>)\">\n {{ item.description }}\n \u003C/slot>\n \u003C/div>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3074,3075,3076],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4394,"Timeline slot issue","2025-06-24T15:13:27Z","https://github.com/nuxt/ui/issues/4394",0.6831344,{"description":3083,"labels":3084,"number":3087,"owner":3029,"repository":3030,"state":3056,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### 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```",[3085,3086],{"name":3020,"color":3021},{"name":3023,"color":3024},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6838827,{"description":3093,"labels":3094,"number":3102,"owner":3029,"repository":3030,"state":3056,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.8.2\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-efufxa?file=app.vue\n\n### Description\n\nCurrently, [the `items` prop in the carousel component is typed as `any`](https://github.com/nuxt/ui/blob/dev/src/runtime/components/elements/Carousel.vue#L81):\r\n\r\nThe issue with typing `items` as `any` is that when using `v-slot=\"{ item }\"`, the `item` will always be typed as `any`. This can make for a poor developer experience, especially when working with more complex item structures, such as creating a carousel of offer cards.\r\n\r\nI believe we can improve this by utilizing [Vue's generics](https://vuejs.org/guide/typescript/overview#generic-components):\r\n\r\nWe could define the generic in the script:\r\n\r\n```html\r\n\u003Cscript lang=\"ts\" generic=\"Item\">\r\n```\r\n\r\nAnd then use the generic in the prop definition:\r\n\r\n```ts\r\nitems: {\r\n type: Array as PropType\u003CItem[]>,\r\n default: () => []\r\n},\r\n```\r\n\r\nIf this change makes sense, I’d be happy to help by submitting a PR.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3095,3096,3099,3101],{"name":3020,"color":3021},{"name":3097,"color":3098},"duplicate","cfd3d7",{"name":3100,"color":3027},"wontfix-v2",{"name":3023,"color":3024},2102,"Carousel - Improve `items` prop typing","2024-09-30T15:25:05Z","https://github.com/nuxt/ui/issues/2102",0.6839698,{"description":3108,"labels":3109,"number":3113,"owner":3029,"repository":3030,"state":3056,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.0\n- Nitro Version: 2.11.6\n- Package Manager: npm@11.1.0\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.2.0, @pinia/nuxt@0.10.1, @vueuse/nuxt@13.0.0, @nuxtjs/i18n@9.3.1, nuxt-security@2.2.0, @nuxt/ui@3.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/wonderful-violet-jrsqy9\n\n### Description\n\nI get a type error when using an array of strings for the `variant` key inside of `compoundVariants´:\n\n```ts\nexport default defineAppConfig({\n ui: {\n colors: {\n primary: \"green\",\n neutral: \"slate\",\n },\n select: {\n compoundVariants: [\n {\n color: \"primary\",\n variant: [\"outline\", \"subtle\"],\n class: \"data-[state='open']:ring\",\n },\n ],\n },\n },\n});\n```\n\n```\napp/app.config.ts:11:11 - error TS2322: Type 'string[]' is not assignable to type 'string'.\n\n11 variant: [\"outline\", \"subtle\"],\n ~~~~~~~\n```\n\nIt does work tho, so its only a type issue I think.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3110,3111,3112],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},3579,"Type error in app config `compoundVariants`","2025-05-02T15:06:25Z","https://github.com/nuxt/ui/issues/3579",0.6847448,{"description":3119,"labels":3120,"number":3134,"owner":3029,"repository":3029,"state":3056,"title":3135,"updated_at":3136,"url":3137,"score":3138},"### 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",[3121,3124,3127,3130,3131],{"name":3122,"color":3123},"discussion","538de2",{"name":3125,"color":3126},"types","2875C3",{"name":3128,"color":3129},"3.x","29bc7f",{"name":3020,"color":3021},{"name":3132,"color":3133},"🔨 p3-minor","FBCA04",23609,"`typeCheck` reports errors from modules when using `tsconfig` rules","2023-11-30T07:26:56Z","https://github.com/nuxt/nuxt/issues/23609",0.6859354,{"description":3140,"labels":3141,"number":3154,"owner":3029,"repository":3030,"state":3056,"title":3155,"updated_at":3156,"url":3157,"score":3158},"### Environment\n\n- Operating System - Ubuntu 22\n- Node Version: 22\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Package Manager: pnpm@10.9.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.17.5\n\n### Reproduction\n\n```javascript\nconst fields = ref([\n {\n name: 'code',\n type: 'otp',\n placeholder: 'Enter 6-digit code',\n otp: {\n length: 6,\n placeholder: '●',\n },\n },\n])\n\nconst submitButtonOptions = computed(() => ({\n label: 'Verify Code',\n loading: loading.value,\n}))\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"flex min-h-screen items-center justify-center p-4\">\n \u003CUPageCard class=\"w-full max-w-md\">\n \u003CUAuthForm\n :schema=\"schema\"\n :state=\"credentials\"\n :fields=\"fields\"\n :loading=\"loading\"\n title=\"Multi-Factor Authentication\"\n subtitle=\"Enter the 6-digit code from your authenticator app to continue.\"\n :submit=\"submitButtonOptions\"\n @submit=\"verifyMFA\"\n >\n \u003Ctemplate #header>\n \u003CNuxtImg\n src=\"/thinkrocket-logo.png\"\n alt=\"ThinkRocket Logo\"\n width=\"100\"\n class=\"mx-auto\"\n preset=\"contain\"\n />\n \u003C/template>\n\n \u003Ctemplate #validation>\n \u003CUAlert\n v-if=\"mfaError\"\n color=\"error\"\n icon=\"i-lucide-alert-circle\"\n :title=\"mfaError\"\n class=\"mb-4\"\n />\n \u003C/template>\n\n \u003Ctemplate #footer>\n \u003Cdiv class=\"text-center space-y-2\">\n \u003Cp class=\"text-sm text-gray-600 dark:text-gray-300\">\n Check your authenticator app for the current code.\n \u003C/p>\n \u003CUButton variant=\"ghost\" size=\"sm\" :loading=\"loading\" @click=\"refreshChallenge\">\n \u003CUIcon name=\"i-lucide-refresh-cw\" class=\"h-4 w-4 mr-1\" />\n Get New Code\n \u003C/UButton>\n \u003C/div>\n \u003C/template>\n \u003C/UAuthForm>\n \u003C/UPageCard>\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\n`:fields` is throwing typescript error. Only an issue with `otp`. Looking in\n\n- `node_modules/.pnpm/@nuxt+ui-pro@3.1.3_@babel+parser@7.27.5_db0@0.3.2_better-sqlite3@11.10.0__embla-carouse_48b559106e80aa1b3007fc5d3af2ab7f/node_modules/@nuxt/ui-pro/dist/runtime/components/AuthForm.vue.d.ts`\n- `node_modules/.pnpm/@nuxt+ui@3.1.3_@babel+parser@7.27.5_db0@0.3.2_better-sqlite3@11.10.0__embla-carousel@8._6f36fdd0332a5dab432a961d27814af8/node_modules/@nuxt/ui/dist/runtime/components/PinInput.vue.d.ts`\n- `node_modules/.pnpm/reka-ui@2.3.1_typescript@5.8.3_vue@3.5.16_typescript@5.8.3_/node_modules/reka-ui/dist/index.d.ts`\n \nI'm not seeing what I'm missing. The [docs](https://ui.nuxt.com/components/auth-form#props) don't give any other details than the example.\n\n```\nVue: Type\n{\n name: string;\n type: string;\n placeholder: string;\n otp: {\n length: number;\n placeholder: string;\n };\n}[]\nis not assignable to type AuthFormField[]\nType\n{\n name: string;\n type: string;\n placeholder: string;\n otp: {\n length: number;\n placeholder: string;\n };\n}\nis not assignable to type AuthFormField\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3142,3143,3146,3147,3150,3151],{"name":3020,"color":3021},{"name":3144,"color":3145},"needs reproduction","CB47CF",{"name":3023,"color":3024},{"name":3148,"color":3149},"nuxt/ui-pro","00dc82",{"name":3026,"color":3027},{"name":3152,"color":3153},"closed-by-bot","ededed",4317,"UAuthForm otp typescript error","2025-06-18T02:14:57Z","https://github.com/nuxt/ui/issues/4317",0.6867141,["Reactive",3160],{},["Set"],["ShallowReactive",3163],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fotnQ-jSIoEDMTvvN-8-GWx-LOqjO9fge6FS5GvpWdq8":-1},"/nuxt/ui/4533"]