` 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",[2974],{"name":2908,"color":2909},2238,"UInput :value not working in v2.18.5","2024-09-25T08:36:59Z","https://github.com/nuxt/ui/issues/2238",0.6966053,{"description":2981,"labels":2982,"number":2988,"owner":2917,"repository":2918,"state":2966,"title":2989,"updated_at":2990,"url":2991,"score":2992},"### Version\n\nv3 latest commit\n\n### Description\n\nI noticed the following behavior:\n\n- When the data prop of a `\u003CUTable>` changes, the rows dont get properly unmounted\n- This results in components within a row to never have `unMounted` being called (only if the amount of rows is less for the ones that get removed)\n- Further this can result in a bugs and unexpected behavior because for components only the props change but the setup function is not called again\n\n### Reproduction\n\nConsider the following simplified example. The badge never changes color. Also if one would use `onMounted`/`onUnmounted` within the badge component they would not get triggered when the data changes (only if the amount of rows change).\n\n**my-badge.vue**\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst props = defineProps\u003C{\n status: 'yes' | 'no';\n}>();\n\nswitch (props.status) {\n case 'yes':\n color = 'success';\n break;\n case 'no':\n color = 'error';\n break;\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUBadge :color variant=\"subtle\">{{ props.status }}\u003C/UBadge>\n\u003C/template>\n```\n\n**my-table.vue**\n```vue\n\u003Cscript setup lang=\"ts\">\n const page = ref(1);\n const { data } = useFetch('url', { query: { page }}); // This gets refetched when `page.value` changes\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUTable :data :columns>\n \u003Ctemplate #status-cell=\"{ row }\">\n \u003CMyBadge :status=\"row.original.status\" />\n \u003C/template>\n \u003C/UTable>\n\u003C/template>\n```\n\n### Additional context\n\nI think this was already the case within v2: There I have a table that contains `\u003CNuxtImg />` tags. When the data changes (e.g. by pagination) the new rows are displayed with the images of the old row until the new images are loaded. That is probably because the `\u003CNuxtImg />` components dont get removed and replaced by all new ones.\n\nLet me know if I should create a reproduction repo\n",[2983,2984,2987],{"name":2908,"color":2909},{"name":2985,"color":2986},"needs reproduction","CB47CF",{"name":2911,"color":2912},3043,"Table rows dont get deleted / unmounted when data changes","2025-03-28T17:35:58Z","https://github.com/nuxt/ui/issues/3043",0.6966456,{"description":2994,"labels":2995,"number":3003,"owner":2917,"repository":2918,"state":2966,"title":3004,"updated_at":3005,"url":3006,"score":3007},"### 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.)",[2996,2997,3000],{"name":2908,"color":2909},{"name":2998,"color":2999},"pro","5BD3CB",{"name":3001,"color":3002},"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.69722813,{"description":3009,"labels":3010,"number":3013,"owner":2917,"repository":2918,"state":2966,"title":3014,"updated_at":3015,"url":3016,"score":3017},"### Description\n\nI need to create custom components including @nuxt/ui components and forward props, emits on this components.\n\nWhen importing (in vue file)\n```ts\nimport type { FormFieldProps, FormFieldSlots } from '@nuxt/ui';\n\nconst props = defineProps\u003CFormFieldProps & { operations?: T[] }>();\nconst slots = defineEmits\u003CFormFieldSlots>();\n\nconst formFieldProps = reactiveOmit(props, ['operations']);\n```\nI receive this error on execution :\n```log\nIdentifier 'appConfig' has already been declared.\n\nInternal server error: Identifier 'appConfig' has already been declared. (105:6) 09:22:04\n Plugin: vite:vue\n File: .../app/pages/ResDossier/components/MyCustomComponent.vue:105:6\n at toParseError (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parse-error.ts:95:45)\n at raise (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/tokenizer/index.ts:1497:19)\n at checkRedeclarationInScope (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/util/scope.ts:155:19)\n at declareName (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/util/scope.ts:109:12)\n at declareName (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/plugins/typescript/scope.ts:89:11)\n at declareNameFromIdentifier (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:739:16)\n at checkIdentifier (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:734:12)\n at checkLVal (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:636:12)\n at parseVarId (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/statement.ts:1605:10)\n at parseVarId (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/plugins/typescript/index.ts:3463:13)\n```\n\nIs there another way to import theses types ?",[3011,3012],{"name":2908,"color":2909},{"name":2911,"color":2912},3124,"how to import type xxxProps / xxxEmits / xxxSlots","2025-01-27T12:26:22Z","https://github.com/nuxt/ui/issues/3124",0.7165491,{"description":3019,"labels":3020,"number":3026,"owner":2917,"repository":2918,"state":2966,"title":3027,"updated_at":3028,"url":3029,"score":3030},"### Description\r\n\r\nFor elements like UAvatar that use images, it would be a good idea to integrate with Nuxt Image for those who have it installed to benefit from image optimizations like setting image format, applying modifiers, and all the other features that Nuxt Image offers.\r\n\r\n### Additional context\r\n\r\n_No response_",[3021,3023,3025],{"name":2937,"color":3022},"a2eeef",{"name":3024,"color":2915},"wontfix-v2",{"name":2911,"color":2912},2078,"[Avatar] Integration with Nuxt Image for built in image optimization","2024-11-07T12:02:04Z","https://github.com/nuxt/ui/issues/2078",0.7189304,["Reactive",3032],{},["Set"],["ShallowReactive",3035],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMUVaUPK46GYRpSIxTiWXMaq3S0GjQTbCmhQZ_Rzkjfo":-1},"/nuxt/ui/2320"]