` 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",[3060],{"name":3031,"color":3032},2238,"UInput :value not working in v2.18.5","2024-09-25T08:36:59Z","https://github.com/nuxt/ui/issues/2238",0.6163979,{"description":3067,"labels":3068,"number":3073,"owner":3020,"repository":3040,"state":3041,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### 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 ?",[3069,3070],{"name":3031,"color":3032},{"name":3071,"color":3072},"v3","49DCB8",3124,"how to import type xxxProps / xxxEmits / xxxSlots","2025-01-27T12:26:22Z","https://github.com/nuxt/ui/issues/3124",0.6440696,{"description":3079,"labels":3080,"number":3084,"owner":3020,"repository":3040,"state":3041,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Description\n\nMultiple UCheckbox can share the same v-model by using an array like :\r\n\r\nhttps://vuetifyjs.com/en/components/checkboxes/#colors\r\n\r\n",[3081],{"name":3082,"color":3083},"question","d876e3",1740,"UCheckbox v-model as array","2025-03-31T08:02:40Z","https://github.com/nuxt/ui/issues/1740",0.66085243,{"description":3090,"labels":3091,"number":3097,"owner":3020,"repository":3020,"state":3041,"title":3098,"updated_at":3099,"url":3100,"score":3101},"## Motivation\r\n\r\nVue is a very international community with a lot of presence in non-english regions like China.\r\n\r\n- Many community members have proposed their help here https://github.com/nuxt/nuxt/discussions/16054\r\n- China have a (non-official ?) Chinese version of the Nuxt docs https://github.com/nuxt/nuxt/discussions/16208 : https://nuxt.com.cn/\\\r\n- A Russian translation has been discussed https://github.com/nuxt/nuxt/discussions/17351\r\n- A Ukrainian translation have been discussed https://github.com/nuxt/nuxt/issues/19926\r\n\r\nFormkit recently released an AI translation for their website docs https://formkit.com/ in 4 languages. \r\n\r\nWe could take a similar approach and combine it with the existing community translations.\r\nIn my opinion, an AI approach needs to be compatible with existing contributions, and manual modifications.\r\n\r\n## Implementation idea\r\n\r\n*Disclaimer: I'm sharing some of my thoughts about how we could build such a system, to gauge community interest in doing so. Suggestion and feedback would be very appreciated!*\r\n\r\nWe would use i18n for the docs website to handle the language strings (related docus issue https://github.com/nuxt-themes/docus/issues/770)\r\nThen to keep the translations in sync with the english source, we could run logic (maybe within the CI), that is triggered when english docs gets merged in nuxt/nuxt, and automatically open PRs for each language with a LLM translation inserted at the right location. \r\nWith such a system, the Nuxt community/team can review the LLM output and modify it before merging it for their language. \r\nAll new additions to the docs must be done in English, so that they are reflected anywhere.\r\nIf translations PRs are an issue for maintainers, we could move all of this to another repo `nuxt-international` or something.\r\n\r\nMany of the Nuxt/Unjs team members already speak 2 or more languages, so we could start out with these languages.\r\nIf this system is successful, it can be expanded and applied to other things, such as the UnJS ecosystem, or integrated with docus\r\n\r\n### Create entire translations from scratch\r\n\r\nWhile working from human written translation is more accurate, we could also experiment with entirely AI written translations. We could build a tool that translates all markdown docs content from the english source into a new language.\r\n\r\n## Bonus\r\n\r\nLook at worldwide trends for Nuxt over the last year : https://trends.google.com/trends/explore?q=nuxt,nuxtjs,nuxt.js&hl=en-GB\r\n\r\nInterestingly enough, there's more search interest for Nuxt in China than in english speaking countries.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/98146ec6-c6d7-479d-afb9-bcb7ee13bf4f\">\r\n\r\nIn fact, the anglosphere rank significantly lower than other areas.\r\n\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3092,3094],{"name":3050,"color":3093},"5319e7",{"name":3095,"color":3096},"discussion","538de2",21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.6808517,{"description":3103,"labels":3104,"number":3105,"owner":3020,"repository":3106,"state":3041,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.6847506,{"description":3112,"labels":3113,"number":3118,"owner":3020,"repository":3040,"state":3041,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[3114,3117],{"name":3115,"color":3116},"enhancement","a2eeef",{"name":3071,"color":3072},2948,"Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.6950871,{"description":3124,"labels":3125,"number":3128,"owner":3020,"repository":3040,"state":3041,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.13.1\n- CLI Version: 3.13.1\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, ui, colorMode, compatibilityDate, icon, sourcemap, experimental, nitro, future, pwa, routeRules, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @vueuse/nuxt@10.11.1, @nuxtjs/mdc@0.6.1, @formkit/auto-animate/nuxt@0.8.2, @vite-pwa/nuxt@0.10.5\n- Build Modules: -\n------------------------------\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\n`style tag`\n\n`Use`\n\n`debug`\n\n\n\n### Description\n\nSorry, I don't know if it's a bad configuration on my part, however the styles in which I use @apply don't work for me.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3126,3127],{"name":3031,"color":3032},{"name":3071,"color":3072},2763,"postcss style not applying","2024-12-05T13:48:59Z","https://github.com/nuxt/ui/issues/2763",0.69601375,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fO-PeTzCQ2YtHnmSaP3PfzYIMCtNqeoymKzw82Rjbfbk":-1},"/nuxt/ui/2923"]