`\n\nit doesn't work that way\n\nI really ask for help!",[2013,2016],{"name":2014,"color":2015},"question","d876e3",{"name":1999,"color":2000},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.7317652,{"description":2023,"labels":2024,"number":2029,"owner":1985,"repository":2005,"state":2030,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2025,2028],{"name":2026,"color":2027},"bug","d73a4a",{"name":1999,"color":2000},3513,"closed","Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.69623476,{"description":2036,"labels":2037,"number":2040,"owner":1985,"repository":2005,"state":2030,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### Environment\n\n\n\nI get this error anytime I try and use \u003CUInput /> even without any other code.\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n`\u003Ctemplate>\n \u003CUContainer>\n \u003CUForm :schema=\"schema\" :state=\"state\" class=\"space-y-4\" @submit=\"onSubmit\">\n \u003CUFormField label=\"Code\" name=\"Code\"\n >\u003CUInput v-model=\"state.code\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { z } from 'zod';\nimport type { FormSubmitEvent } from '#ui/types';\n\nconst supabase = useSupabaseClient();\nconst toast = useToast();\n\n//Form\nconst schema = z.object({\n code: z.string().min(3),\n});\n\ntype Schema = z.output\u003Ctypeof schema>;\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n code: undefined,\n});\n\nasync function onSubmit(event: FormSubmitEvent\u003CSchema>) {\n toast.add({\n title: 'Success',\n description: 'The form has been submitted.',\n color: 'success',\n });\n console.log(event.data);\n}\n\u003C/script>\n`\n\n### Description\n\nUInput causes an error\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2038,2039],{"name":2026,"color":2027},{"name":1999,"color":2000},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.69662964,{"description":2046,"labels":2047,"number":2050,"owner":1985,"repository":2005,"state":2030,"title":2051,"updated_at":2052,"url":2053,"score":2054},"### Description\n\nFor custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties `touched` and `dirty` exposed.\n\n- `Touched` (opposite of `untouched`): A field is considered touched when a user has focused it OR changed it's value\n- `Dirty` (opposite of `pristine`): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.\n\nYou can currently work around most of these by using a computed on the exposed `errors` ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.\n\n### Additional context\n\n_No response_",[2048,2049],{"name":1996,"color":1997},{"name":1999,"color":2000},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.7139665,{"description":2056,"labels":2057,"number":2064,"owner":1985,"repository":1985,"state":2030,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Environment\r\n\r\n System:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i3-10100F CPU @ 3.60GHz \r\n Memory: 8.10 GB / 15.93 GB\r\n Binaries:\r\n Node: 20.11.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - F:\\Other\\nodejs\\global\\yarn.CMD\r\n npm: 10.2.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 8.6.0 - F:\\Other\\nodejs\\global\\pnpm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.36)\r\n Internet Explorer: 11.0.19041.1566\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-7jsgdv?file=nuxt.config.js\r\n\r\n### Describe the bug\r\nmy test site:http://nuxt2.cqyx.vip\r\nWhen I use the npm run generate,cdn prefix of //, the example.\r\n{.\r\nbuild: {.\r\npublicPath: \"//static.cqyx.vip/nuxt2/\"\r\n}.\r\n}.\r\nStatic resources will report an error and there will be two manifest.js references\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_",[2058,2061],{"name":2059,"color":2060},"pending triage","E99695",{"name":2062,"color":2063},"2.x","d4c5f9",25989,"generate bug","2024-06-30T09:21:40Z","https://github.com/nuxt/nuxt/issues/25989",0.7169555,{"description":2070,"labels":2071,"number":2074,"owner":1985,"repository":2005,"state":2030,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Description\n\nI was trying to add a bit of margin around the Slideover to look like this:\n\n\n\nI think it can be done cleanly if there was a `\u003Cdiv>` wrapping the whole [DialogContent](https://github.com/nuxt/ui/blob/71728d3c3fa95255db03448c8b87fb75bc2d805c/src/runtime/components/Slideover.vue#L129C7-L129C21)\n\nHow do you suggest to achieve it? \nThank you",[2072,2073],{"name":2014,"color":2015},{"name":1999,"color":2000},3390,"How to add margins around the Slideover panel?","2025-02-25T15:36:40Z","https://github.com/nuxt/ui/issues/3390",0.7179637,{"description":2080,"labels":2081,"number":2084,"owner":1985,"repository":2005,"state":2030,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\n\nirrelevant\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"@nuxt/ui\": \"3.0.0-alpha.9\",\n\n### Reproduction\n\n\n\n\n### Description\n\ncontributes to failing google lighthouse scores for this violation\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2082,2083],{"name":2026,"color":2027},{"name":1999,"color":2000},2725,"UBreadcrumb accessibility issue - Lists do not contain only \u003Cli> elements and script supporting elements (\u003Cscript> and \u003Ctemplate>).","2024-12-05T13:48:54Z","https://github.com/nuxt/ui/issues/2725",0.718749,{"description":2090,"labels":2091,"number":2093,"owner":1985,"repository":2005,"state":2030,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Description\n\nI am using the UFormGroup component. My use case is I want to have the label and/or description set dynamically based on a value coming from my Api.\n\nIs there any way of doing it and if yes were can I find some example?\n\nThank you\n",[2092],{"name":2014,"color":2015},3337,"UFormGroup dynamic Description","2025-02-17T02:56:17Z","https://github.com/nuxt/ui/issues/3337",0.71880484,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"GaUcemEwuUSQO5QJN-X3NjfXh7Gb6AKKu6Xu5WKOrQg":-1},"/nuxt/ui/3226"]