` change it to `\u003CUInput :model-value=\"'12714274'\" readonly />`\r\n\r\n\r\n\r\n--------- \r\n\r\n\r\n### Version\r\n\r\nedit: v2.18.5\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-uds7la?file=app.vue\r\n\r\n### Description\r\n\r\nSo i have a few grouped form inputs and noticed all values being empty since last update, reverted back to 2.18.4 and worked again. \r\n\r\n_(👀 or you can tell me im using it wrong)_\r\n\r\n### Why i am using :value= ? \r\n\r\n```\r\n\u003CUInput\r\n :value=\"firstname\"\r\n @input=\"$emit('update:firstname', $event.target.value)\"\r\n />\r\n \u003CUInput\r\n :value=\"lastname\"\r\n @input=\"$emit('update:lastname', $event.target.value)\"\r\n />\r\n```\r\n\r\nand using \r\n```\r\n\u003CAccountFormDetails\r\n v-model:firstname=\"formState.firstname\"\r\n v-model:lastname=\"formState.lastname\"\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```shell-script\r\nno logs,no errors\r\n```\r\n\r\nedit: added repro\r\nedit: pinpointed on 2.18.5, this happened between 18.4 and 18.5",[3184],{"name":3149,"color":3150},2238,"UInput :value not working in v2.18.5","2024-09-25T08:36:59Z","https://github.com/nuxt/ui/issues/2238",0.6765607,{"description":3191,"labels":3192,"number":3194,"owner":3138,"repository":3155,"state":3156,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.15.1\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/device@3.2.4, @vueuse/nuxt@12.0.0, @nuxt/image@1.8.1, @nuxt/eslint@0.7.2, @nuxt/test-utils/module@3.15.1, @nuxt/ui@2.19.2, @pinia/nuxt@0.8.0, pinia-plugin-persistedstate/nuxt\n- Build Modules: -\n\n### Version\n\n2.19.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jqjcwwoz\n\n### Description\n\nThe variant for `outline` and `subtle` doesn't have the corresponding ring color class when using any colors except `primary` and `red`.\n\nThe ring color stays blue-ish and i can see that the css class is missing.\n\nThis bug exist for both dark and light modes.\n\n\n\n### Additional context\n\nThis bug only occurs when using the `UBadge` inside a component. It also occurs only when passing the badge colors through the component props.\n\n\n\n### Logs\n\n```shell-script\n\n```",[3193],{"name":3149,"color":3150},2861,"UBadge: Wrong ring color in outline and subtle variants","2025-01-13T16:34:19Z","https://github.com/nuxt/ui/issues/2861",0.67897904,{"description":3200,"labels":3201,"number":3206,"owner":3138,"repository":3155,"state":3156,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Environment\n\n- OS : Windows 11\n- Node : 20.14.0 \n- Nuxt: lastest\n- Nuxt prisma : lastest\n\n### Version\n\n2.19.1\n\n### Reproduction\n\ninit lastest nuxt 3\nadd nuxt prisma module\nadd nuxt ui module\n\n` ERROR RollupError: node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts (2:8): Expected ';', '}' or \u003Ceof> (Note that you need plugins to import files that are not JavaScript) nitro 21:27:12 \n\n\n1: import { PrismaClient } from \"@prisma/client\";\n2: declare const prismaClientSingleton: () => PrismaClient\u003Cimport(\".prisma/client\").Prisma.PrismaClientOptions, never, i...\n ^\n3: declare const prisma: PrismaClient\u003Cimport(\".prisma/client\").Prisma.PrismaClientOptions, never, import(\"@prisma/client...\n4: export type CustomPrismaClient = ReturnType\u003Ctypeof prismaClientSingleton>;`\n\n### Description\n\nwhen remove `'@nuxt/ui'` from modules: [''] in nuxt.config.ts it's work can use npm run dev\nbut if add `'@nuxt/ui'` it''s error\n\n` ERROR RollupError: node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts (2:8): Expected ';', '}' or \u003Ceof> (Note that you need plugins to import files that are not JavaScript) nitro 21:27:12 \n\n\n1: import { PrismaClient } from \"@prisma/client\";\n2: declare const prismaClientSingleton: () => PrismaClient\u003Cimport(\".prisma/client\").Prisma.PrismaClientOptions, never, i...\n ^\n3: declare const prisma: PrismaClient\u003Cimport(\".prisma/client\").Prisma.PrismaClientOptions, never, import(\"@prisma/client...\n4: export type CustomPrismaClient = ReturnType\u003Ctypeof prismaClientSingleton>;`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3202,3203],{"name":3149,"color":3150},{"name":3204,"color":3205},"duplicate","cfd3d7",2813,"nuxt/ui conflict with nuxt/prisma","2024-12-04T08:33:58Z","https://github.com/nuxt/ui/issues/2813",0.69145876,{"description":3212,"labels":3213,"number":3221,"owner":3138,"repository":3155,"state":3156,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Environment\n\nBuild error on vercel.app and on local windows 10, both on build and dev.\n\n### Version\n\nv1.4.4 @nuxt/ui-pro - Saas Template\n\n### Reproduction\n\nInstall a clean saas template.\nEnable typescript check in nuxt.config\n\nTry to deploy it on vercel.\n\nAnd try to copy/paste the url in a facebook post.\n\nHere is a 100% clean saas template, without typeCheck enabled:\nhttps://stackblitz.com/~/github.com/LutherApp/codespace-project\n\n(This is a copy of my [github repo](https://github.com/LutherApp/codespace-project))\n\n### Description\n\nOn build there will be \n## errors on the \"title\"-variable\nError-msg:\nObject literal may only specify known properties, and 'title' does not exist in type 'OgImageOptions\u003C\"NuxtSeo\"> | OgImagePrebuilt'. (etc.)\n\n## \"authors\"- and \"title\"-variable in blog/index\n3 x Type 'bla bla bla' is not assignable to type 'bla bla bla'.\n1 x Property 'avatar' is optional in type 'bla bla bla' but required in type 'bla bla bla'.\n\n## Fix\nI was adding this workaround for typecheck in three or four files:\n```\n// @ts-expect-error Object literal may only specify known properties, and 'title' does not exist in type 'OgImageOptions\u003C\"NuxtSeo\"> | OgImagePrebuilt'.\n```\n\nIn blog/index.vue a was adding this lines in the template in front of `UPageBody` (in blog/index.vue):\n``` \n\u003C!--\n @vue-expect-error The variable authors throws four errors;\n 3 x Type 'bla bla bla' is not assignable to type 'bla bla bla'.\n 1 x Property 'avatar' is optional in type 'bla bla bla' but required in type 'bla bla bla'.\n -->\n```\n\n## seo info from the page missing on facebook\nThere is still noe data about the page on facebook. \n(Other nuxt-content I have made earlier have this info when I copy/paste the url to facebook.)\n\n## Any questions to this issue?\nPlease add some questions to get more info about this issues. (This was written faster than normal.)",[3214,3215,3218],{"name":3149,"color":3150},{"name":3216,"color":3217},"pro","5BD3CB",{"name":3219,"color":3220},"upstream","78bddb",2415,"og:fields in my 100% clean saas template doesn't shows on facebook, and your own public saas template don't show the og:image","2024-10-22T09:40:37Z","https://github.com/nuxt/ui/issues/2415",0.6923063,{"description":3227,"labels":3228,"number":3233,"owner":3138,"repository":3155,"state":3156,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Description\n\nThis is highly experimental and potentially canceled, I'm opening this issue to both track down best approach and naming conventions before working on a PR. **I'll update this issue as I work on it**\n\n## Idea\n\nWith the current [Design Tokens](https://ui3.nuxt.dev/getting-started/theme#tokens) we control colors, radius and container width. This greatly simplifies both prototyping process and agencies working on templates built with Nuxt UI.\nPersonally there is one missing feature about colors: their opacity/shades, that you can find in the various states and variants.\n\nTaking in example any variant for the `Button` component, we have a set of hardcoded opacities (in this case: `/25`, `/10` and `/15`):\nhttps://github.com/nuxt/ui/blob/7f64198a70104436f39f2f9d8527df0508fd84f6/src/theme/button.ts#L91-L95\n\nIn a design first approach, especially when working on bigger projects, it is often to have the brand colors pre-defined for things like hover, disabled and such. This means that, if the project requires them, you are most probably forced to edit each very component's color in the `app.config`.\n\n### What we have\n\nWe auto generate a series of css variables as `--ui-{color}` based on `ui.theme.colors` inside the `nuxt.config.ts`. Then use them as `(text/bg/ring)-[var(--ui-{color})]/{opacity}` both as base and with modifiers (hover, disabled and so on).\n\nThey are used 40 times in total (7 unique: `/10`, `/15`, `/20`, `/25`, `/50`, `/75` and `/90`), distributed as:\n- **24** on `--ui-{color}`\n - ...\n- **7** on `--ui-bg-elevated`\n - `/50` for bg, hover and `data-highlighted`\n- **4** on `--ui-bg-accented`\n - `/75` for hover\n- **3** on `--ui-bg`\n - `/75` for pinned and sticky in UTable\n- **2** on `--ui-bg-inverted`\n - `/20` for `data-[highlighted]`\n - `/90` for hover\n\n### My approach\n\nI would like to group the various opacities into two categories: those that are actual opacities (mainly for `--ui-bg*`) and those that are for colors.\n- for the background ones I would mostly group them as three type of opacities (potentially creating three named variants)\n- for colors I would simply replace them with another named css variable, with follows the naming convention of `--ui-bg-(elevated/inverted/accented/*)`, becoming something like `--ui-{color}-(elevated/inverted/accented/*)`. For its default value I would use `color-mix(oklab, var(--ui-{color}) {opacity});`, keeping the current functionality of requiring a single starting color.\n\n### Additional context\n\n_No response_",[3229,3232],{"name":3230,"color":3231},"enhancement","a2eeef",{"name":3152,"color":3153},2941,"[Design Tokens] add `opacity` modifiers","2025-02-07T15:47:50Z","https://github.com/nuxt/ui/issues/2941",0.6950538,{"description":3239,"labels":3240,"number":3243,"owner":3138,"repository":3155,"state":3156,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-security@2.1.4, @nuxtjs/seo@2.0.0-rc.23, @nuxt/ui@3.0.0-alpha.9, @storyblok/nuxt@6.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n1. use sm:space-x-8 class in your component\n2. build it , with `npm run build`\n3. open in a browser and check the styles for this class\n\n### Description\n\nIn development env the styles are ok\n\nafter build the styles are missing\n\nfor example: sm:space-x-8\n\nDevlopment\n\n\n\nProduction\n\n\nThank you\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3241,3242],{"name":3149,"color":3150},{"name":3152,"color":3153},2738,"After build, the styles are missing","2025-02-08T21:06:21Z","https://github.com/nuxt/ui/issues/2738",0.69994664,["Reactive",3249],{},["Set"],["ShallowReactive",3252],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZRIzOCtd5QkRmZkdPDyVz76Yxi98GvJFu2hR0Jm5Uz4":-1},"/nuxt/ui/3148"]