\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3086,3089],{"name":3087,"color":3088},"question","d876e3",{"name":3023,"color":3024},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.6998669,{"description":3096,"labels":3097,"number":3101,"owner":3029,"repository":3040,"state":3031,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### 🐛 The bug\n\n\r\n```\r\n ERROR(vue-tsc) Binding element 'Vimeo' implicitly has an 'any' type.\r\n FILE D:/dev/test1/node_modules/.pnpm/@nuxt+scripts@0.8.4_@nuxt+devtools@1.4.1_rollup@4.21.2_vite@5.4.3_@types+node@22.5.4_terser@5_npscaliduljzxdqaosyipgid7y/node_modules/@nuxt/scripts/dist/runtime/components/ScriptVimeoPlayer.vue:187:21\r\n\r\n 185 |\r\n 186 | onMounted(() => {\r\n > 187 | onLoaded(async ({ Vimeo }) => {\r\n | ^^^^^\r\n 188 | const vimeoOptions = props.vimeoOptions || {}\r\n 189 | if (!vimeoOptions.id && props.id) {\r\n 190 | vimeoOptions.id = props.id\r\n\r\n ERROR(vue-tsc) Parameter 'instance' implicitly has an 'any' type.\r\n FILE D:/dev/test1/node_modules/.pnpm/@nuxt+scripts@0.8.4_@nuxt+devtools@1.4.1_rollup@4.21.2_vite@5.4.3_@types+node@22.5.4_terser@5_npscaliduljzxdqaosyipgid7y/node_modules/@nuxt/scripts/dist/runtime/components/ScriptYouTubePlayer.vue:61:19 \r\n\r\n 59 | }\r\n 60 | onMounted(() => {\r\n > 61 | onLoaded(async (instance) => {\r\n | ^^^^^^^^\r\n 62 | const YouTube: typeof YT & { ready: (fn: () => void) => void } = await instance.YT\r\n 63 | await new Promise\u003Cvoid>((resolve) => {\r\n 64 | if (typeof YT.Player === 'undefined')\r\n\r\n[vue-tsc] Found 2 errors. Watching for file changes.\r\n```\r\n\r\n\r\n\r\nWhen using [Nuxt Devtools](https://github.com/nuxt/devtools) in typescript strict mode and enabling type check, these two errors will be occurred.\r\n\r\n```typescript\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n modules: ['@nuxt/scripts'],\r\n typescript: {\r\n typeCheck: true,\r\n strict: true\r\n },\r\n})\r\n```\r\n\r\nI think this might be related to https://github.com/nuxt/scripts/issues/217#issuecomment-2336846827. These are same errors as what in that comment.\r\n\r\nVersions: \r\n@nuxt/scripts: 0.8.4\r\n@nuxt/devtools : 1.4.1\r\nvue-tsc: 2.0.29\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/~/github.com/ifrvn/nuxt-scripts-issue-test\n\n### 🌈 Expected behavior\n\nno error\n\n### ℹ️ Additional context\n\n_No response_",[3098],{"name":3099,"color":3100},"bug","d73a4a",256," ERROR(vue-tsc) Binding element 'Vimeo' implicitly has an 'any' type.","2024-09-09T14:05:17Z","https://github.com/nuxt/scripts/issues/256",0.70192295,{"description":3107,"labels":3108,"number":3112,"owner":3029,"repository":3029,"state":3031,"title":3113,"updated_at":3114,"url":3115,"score":3116},"Nuxt 1.0rc4 apparently tries to use the `type` property on an object from a list passed to `v-for` when rendering, resulting in an error like this:\r\n\r\n\u003Cimg width=\"944\" alt=\"screen shot 2017-08-19 at 7 36 45 am\" src=\"https://user-images.githubusercontent.com/12291/29485926-6286990e-84b1-11e7-9033-3967d02c3150.png\">\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1260\">#c1260\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3109],{"name":3110,"color":3111},"2.x","d4c5f9",1418,"Type property on objects","2023-01-18T15:41:44Z","https://github.com/nuxt/nuxt/issues/1418",0.70409614,{"description":3118,"labels":3119,"number":3124,"owner":3029,"repository":3125,"state":3031,"title":3126,"updated_at":3127,"url":3128,"score":3129},"There is an issue during the resize on the gradient:\r\n\r\nhttps://user-images.githubusercontent.com/904724/177326570-64a34124-592c-474f-975e-02b854c75c53.mp4\r\n\r\nAlso, could we handle the 3D gem like on Nuxt v3 docs?\r\n\r\n\r\n\r\n",[3120,3122],{"name":3099,"color":3121},"ff281a",{"name":3020,"color":3123},"1ad6ff",781,"nuxt.com","[Home] Hero improvements","2023-09-05T08:18:36Z","https://github.com/nuxt/nuxt.com/issues/781",0.70463073,{"description":3131,"labels":3132,"number":3135,"owner":3029,"repository":3030,"state":3031,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nIn version 2 of Nuxt UI, a `click` property can be defined in dropdown `items` props. In V3, this feature has not yet been implemented wet.\n\n### Additional context\n\n_No response_",[3133,3134],{"name":3020,"color":3021},{"name":3023,"color":3024},2450,"[DropdownMenu] - Add click properties to items props for handle custom click event","2024-10-24T12:30:29Z","https://github.com/nuxt/ui/issues/2450",0.7049974,["Reactive",3141],{},["Set"],["ShallowReactive",3144],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJPufM9pFKBwfHL0FMESsTgnj2kSMAKDDIVFVDDmm72k":-1},"/nuxt/nuxt.com/685"]