\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2043,2046,2049],{"name":2044,"color":2045},"bug","d73a4a",{"name":2047,"color":2048},"needs reproduction","CB47CF",{"name":2003,"color":2004},3546,"closed","`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.72455674,{"description":2057,"labels":2058,"number":2062,"owner":1991,"repository":2063,"state":2051,"title":2064,"updated_at":2065,"url":2066,"score":2067},"I have a custom composable (`useConsent`), which I am trying to mock. \r\nI'm importing the composable like so:\r\n\r\n`import { useConsent, useHead } from '#imports'`.\r\n\r\nThe import is recognized in `packages/vitest-environment-nuxt/src/modules/mock.ts`:\r\n```\r\n{\r\n name: \"default\",\r\n as: \"useConsent\",\r\n from: \"[...]/src/runtime/composables/useConsent.ts\",\r\n priority: undefined,\r\n}\r\n```\r\n\r\nEven though the import is recognized and no `\"Cannot find import to mock\"` error is thrown, the import is not mocked.\r\nIn the same file I am mocking `useHead`, that one is mocked without any issues.\r\n\r\nUsing `nuxt-vitest@0.8.4`\r\n",[2059],{"name":2060,"color":2061},"vitest-environment","b60205",524,"test-utils","custom composable without function name not mocked with `mockNuxtImport`","2023-12-02T00:17:13Z","https://github.com/nuxt/test-utils/issues/524",0.7309727,{"description":2069,"labels":2070,"number":2072,"owner":1991,"repository":2009,"state":2051,"title":2073,"updated_at":2074,"url":2075,"score":2076},"### Description\n\nI would like to style my Radio component like this -\n\n\nBut Nuxt UI default styling gives me this. Without much ability to customize -\n\n\nI achieved the first styling in a very hacky way. I saw the DOM of the `\u003CURadioGroup>` component and used deep selector to style child tags. Some class selectors that are used are from tailwind like the items-start (styling code in the comment section). Not the best way, but it works.\n\nIs there a more elegant and straightforward way to do this?\n",[2071],{"name":2032,"color":2033},2950,"NuxtUI custom styling of URadioGroup component","2024-12-22T15:40:17Z","https://github.com/nuxt/ui/issues/2950",0.7346045,{"description":2078,"labels":2079,"number":2082,"owner":1991,"repository":2009,"state":2051,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\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```",[2080,2081],{"name":2032,"color":2033},{"name":2003,"color":2004},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.73488194,{"description":2088,"labels":2089,"number":2091,"owner":1991,"repository":2092,"state":2051,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### 🐛 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_",[2090],{"name":2044,"color":2045},256,"scripts"," ERROR(vue-tsc) Binding element 'Vimeo' implicitly has an 'any' type.","2024-09-09T14:05:17Z","https://github.com/nuxt/scripts/issues/256",0.7373845,{"description":2098,"labels":2099,"number":2101,"owner":1991,"repository":2023,"state":2051,"title":2102,"updated_at":2103,"url":2104,"score":2105},"Only company links:\n\n\n",[2100],{"name":1985,"color":2018},482,"Footer should disappear","2022-05-11T11:50:35Z","https://github.com/nuxt/nuxt.com/issues/482",0.7409114,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"C2I4NTs25RZoZcvapY5-7aUSyilJVcvm4mr9bHT0Hm8":-1},"/nuxt/ui/2269"]