\r\n \u003C/UFormGroup>\r\n \u003C/UForm>\r\n\u003C/template>\r\n```\r\n\r\n\u003Cimg width=\"1239\" alt=\"chrome\" src=\"https://github.com/user-attachments/assets/750c2b77-79a2-4aa1-b29c-1fd36db0cfa0\">\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2001],{"name":1985,"color":1986},2126,"closed","Chrome: Label 'for' attribute mismatch with form field IDs in URadioGroup","2024-09-06T16:59:18Z","https://github.com/nuxt/ui/issues/2126",0.7030262,{"description":2009,"labels":2010,"number":2014,"owner":1991,"repository":2015,"state":2003,"title":2016,"updated_at":2017,"url":2018,"score":2019},"Creating this kind of a component:\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>SetupExportComponent\u003C/h1>\r\n \u003Cpre>{{ myProp }}\u003C/pre>\r\n \u003Cpre>{{ setupMyProp }}\u003C/pre>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003C!-- this works!\r\n\u003Cscript setup lang=\"ts\">\r\nconst props = defineProps\u003C{ myProp: string }>()\r\nconst setupMyProp = 'X' + props.myProp\r\n\u003C/script>\r\nFollowing script is a valid Vue 3 way to define a component\r\n-->\r\n\r\n\u003Cscript lang=\"ts\">\r\nexport default defineComponent({\r\n props: {\r\n myProp: {\r\n type: String,\r\n required: true\r\n }\r\n },\r\n setup(props) {\r\n return {\r\n setupMyProp: 'X' + props.myProp\r\n }\r\n }\r\n})\r\n\u003C/script>\r\n```\r\n\r\nWhen trying to `mountSuspended` this, it doesn't handle the props or the data returned from the `setup` function. Defining it with the `script setup` works correctly. I have the code with the unit test in my fork and will make a PR about it. I can maybe fix it, too, if I get some hints were to begin.",[2011],{"name":2012,"color":2013},"vitest-environment","b60205",606,"test-utils","defineComponent style components don't work with mountSuspended","2023-12-02T17:18:48Z","https://github.com/nuxt/test-utils/issues/606",0.71083754,{"description":2021,"labels":2022,"number":2027,"owner":1991,"repository":1992,"state":2003,"title":2028,"updated_at":2029,"url":2030,"score":2031},"### Description\n\nHi,\r\n\r\nThe Icon component doesn't have a UI prop like most components. This prevent users from applying a CSS class to all instances of Icon. IMO, this is a really small harmless change, that would align Icons with the rest of the library.\r\n\r\nAs of v2.18.4, this is true for:\r\n- [ ] Form\r\n- [ ] Icon\r\n- [ ] Link\r\n\r\nAs a workaround, it's always possible to create a wrapper component.\r\n\r\n```vue\r\n\u003Cscript setup>\r\ndefineProps(['name', 'ui']);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cu-icon :name=\"name\" :class=\"ui.base\" />\r\n\u003C/template>\r\n``` \r\n\r\nBy the way, [the doc state](https://ui.nuxt.com/getting-started/theming#ui-prop) that \"Each component has a ui prop\". Which is not true then.\n\n### Additional context\n\n_No response_",[2023,2026],{"name":2024,"color":2025},"enhancement","a2eeef",{"name":1988,"color":1989},2094,"Some component doesn't have a UI prop","2025-03-17T14:27:40Z","https://github.com/nuxt/ui/issues/2094",0.71733415,{"description":2033,"labels":2034,"number":2041,"owner":1991,"repository":1992,"state":2003,"title":2042,"updated_at":2043,"url":2044,"score":2045},"### Description\n\nhey guys,\n\nFor some reason I can't get the `@apply` function in css working with Nuxt UI V3?\n\nIf I do something like this in the `\u003Cstyle>` section of a component: \n\n```\n\u003Cstyle scoped>\nh1 {\n @apply text-4xl;\n}\n\u003C/style>\n```\n\nI get this error: \n\n\n```zsh\n\n ERROR x Build failed in 694ms 4:30:24 PM\n\n\n ERROR Nuxt Build Error: [@tailwindcss/vite:generate:build] Cannot apply unknown utility class: text-4xl \n\n```\n\nWeirdly if I do `class=\"text-4xl\"` it works? Also If I comment out the `\u003Cstyle>` section above it also works? What's going on here? it's like the `@apply` function isn't setup or recognised? How do I go about debugging this?\n",[2035,2038],{"name":2036,"color":2037},"question","d876e3",{"name":2039,"color":2040},"v3","49DCB8",3193,"@apply - `Cannot apply unknown utility class`","2025-01-28T16:53:52Z","https://github.com/nuxt/ui/issues/3193",0.7282393,{"description":2047,"labels":2048,"number":2051,"owner":1991,"repository":2052,"state":2003,"title":2053,"updated_at":2054,"url":2055,"score":2056},"",[2049],{"name":2024,"color":2050},"1ad6ff",675,"nuxt.com","[Docs] Improve prose design","2022-07-07T12:30:55Z","https://github.com/nuxt/nuxt.com/issues/675",0.72999644,{"description":2058,"labels":2059,"number":2063,"owner":1991,"repository":1991,"state":2003,"title":2064,"updated_at":2065,"url":2066,"score":2067},"### Environment\n\nStackblitz Sandbox\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-7wcdxads?file=app.vue,components%2FErrorContent.vue\n\n### Describe the bug\n\nI want to intercept errors within the component as much as possible, so that they only affect the current component and do not cause the entire page to crash. However, I tried the following three methods (all based on onErrorCaptured), and they work fine when useFetch is not used on the page. But once useFetch is used, the page directly returns a 500 status code, and I am unable to intercept the relevant errors to prevent the page from crashing.\n\nhttps://cn.vuejs.org/api/composition-api-lifecycle#onerrorcaptured\nhttps://nuxt.com/docs/getting-started/error-handling#vue-errors\nhttps://nuxt.com/docs/api/components/nuxt-error-boundary\n\nI hope there is a way to intercept errors within the component when using useFetch, so that it doesn't cause the entire page to display a 500 error, thanks.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2060],{"name":2061,"color":2062},"pending triage","E99695",30917,"fetchData causes onErrorCaptured to be unable to capture errors","2025-02-22T20:46:13Z","https://github.com/nuxt/nuxt/issues/30917",0.73291904,{"description":2069,"labels":2070,"number":2073,"owner":1991,"repository":1992,"state":2003,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.20.4\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.18.7\n- Build Modules: -\n\n### Version\n\nv3\n\n### Reproduction\n\nCreat new project with nuxi\n\nInstall nuxt/ui\n\n### Description\n\nCannot destructure property 'nuxt' of 'this' as it is undefined.\n\nNot working on fresh project\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2071,2072],{"name":1985,"color":1986},{"name":2039,"color":2040},2442,"Cannot destructure property 'nuxt' of 'this' as it is undefined.","2024-10-23T20:22:23Z","https://github.com/nuxt/ui/issues/2442",0.7417115,{"description":2079,"labels":2080,"number":2082,"owner":1991,"repository":1992,"state":2003,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Description\n\nWhen using `USelectMenu` component (v2) with `multiple`, would it be possible to have a new prop to pass a translated string for this line: https://github.com/nuxt/ui/blob/ede7d7c2b7009c375dee491619c9f1c26f90eb6a/src/runtime/components/forms/SelectMenu.vue#L387\n\n### Additional context\n\n\n",[2081],{"name":2024,"color":2025},2333,"[USelectMenu] translate \"selected\" string","2025-01-15T11:12:15Z","https://github.com/nuxt/ui/issues/2333",0.74356604,{"description":2088,"labels":2089,"number":2091,"owner":1991,"repository":1992,"state":2003,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.12.0\r\n- Nuxt Version: 3.10.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.5.0\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/ui@2.18.6\r\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/k6rsz6?file=%2Fapp.vue%3A1%2C1\n\n### Description\n\nI'm trying to add types for a `ref` to a `UForm` component, but when I tried to use the `setErrors` method there was the following typescript error:\r\n\r\n```\r\nProperty 'setErrors' does not exist on type\r\n'CreateComponentPublicInstanceWithMixins\u003CReadonly\u003CExtractPropTypes\u003C{ schema: { type: PropType\u003CZodSchema> | PropType\u003CYupObjectSchema\u003Cany>> | PropType\u003CJoiSchema> | PropType\u003Cany>; default: any; }; state: { type: ObjectConstructor; required: true; }; validate: { ...; }; validateOn: { ...; }; }>> & Readonly\u003C...>, ... 24 m...'.\r\nDid you mean 'errors'?\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2090],{"name":1985,"color":1986},2292,"Property 'setErrors' does not exist on type","2024-10-06T17:50:16Z","https://github.com/nuxt/ui/issues/2292",0.7449053,["Reactive",2097],{},["Set"],["ShallowReactive",2100],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"rvfQaBJq9yYECJ6ttK_ttU9oL5cT3LA4wfPW5mleEw4":-1},"/nuxt/icon/139"]