",[2010,2013,2016],{"name":2011,"color":2012},"enhancement","a2eeef",{"name":2014,"color":2015},"v3","49DCB8",{"name":1999,"color":2000},3270,"[Feature request] Toast hide progress in app.config","2025-02-09T17:11:11Z","https://github.com/nuxt/ui/issues/3270",0.707376,{"description":2023,"labels":2024,"number":2030,"owner":1985,"repository":2002,"state":1987,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Environment\n\n- node: 22\n- nuxt: 3.15.4\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nnot required\n\n### Description\n\nrun \"npx nuxi typecheck\"\n\n```\n Argument of type '{ item: T; index: number; }' is not assignable to parameter of type '({ leading: SlotProps\u003CT>; default: SlotProps\u003CT>; trailing: SlotProps\u003CT>; content: SlotProps\u003CT>; } & Record\u003Cstring, SlotProps\u003CT>> & (T[\"slot\"] extends string ? Record\u003C...> : Record\u003C...>))[string] & SlotProps\u003C...> extends (props: infer P) => any ? P : {}'.\n\n137 \u003Cslot :name=\"item.slot || 'content'\" :item=\"item\" :index=\"index\">\n```\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2025,2026,2027],{"name":1996,"color":1997},{"name":2014,"color":2015},{"name":2028,"color":2029},"upstream","78bddb",3405,"type errors on slots with vue-tsc 2.2.4","2025-03-19T22:45:04Z","https://github.com/nuxt/ui/issues/3405",0.7105808,{"description":2036,"labels":2037,"number":2043,"owner":1985,"repository":2002,"state":2044,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### 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.)",[2038,2039,2042],{"name":1996,"color":1997},{"name":2040,"color":2041},"pro","5BD3CB",{"name":2028,"color":2029},2415,"closed","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.5980182,{"description":2050,"labels":2051,"number":2055,"owner":1985,"repository":1986,"state":2044,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Environment\n\nNot needed\n\n### Reproduction\n\nNot necessary, any SSR/Prerender Nuxt will fail\n\n### Describe the bug\n\nI'm just creating this issue to warn anyone that is using Cloudflare with Nuxt SSR\r\n\r\nDISABLE ASSET MINIFICATION, it breaks Vue hydration\r\n\r\n\r\nI've spent weeks trying to fix it, and it was as simple as unchecking these boxes, hope it helps anyone\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2052],{"name":2053,"color":2054},"documentation","9DE2BA",1457,"SSR Issues with Coudflare Pages (SOLVED)","2023-12-27T17:11:13Z","https://github.com/nuxt/nuxt.com/issues/1457",0.61408234,{"description":2061,"labels":2062,"number":2064,"owner":1985,"repository":2002,"state":2044,"title":2065,"updated_at":2066,"url":2067,"score":2068},"# tldr\r\nWhen using nuxt UI v2.18.5 or higher -> `\u003CUInput value=\"'12714274'\" readonly />` 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",[2063],{"name":1996,"color":1997},2238,"UInput :value not working in v2.18.5","2024-09-25T08:36:59Z","https://github.com/nuxt/ui/issues/2238",0.62523717,{"description":2070,"labels":2071,"number":2074,"owner":1985,"repository":2002,"state":2044,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### 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 ?",[2072,2073],{"name":1996,"color":1997},{"name":2014,"color":2015},3124,"how to import type xxxProps / xxxEmits / xxxSlots","2025-01-27T12:26:22Z","https://github.com/nuxt/ui/issues/3124",0.63251656,{"description":2080,"labels":2081,"number":2087,"owner":1985,"repository":1985,"state":2044,"title":2088,"updated_at":2089,"url":2090,"score":2091},"## 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).",[2082,2084],{"name":2053,"color":2083},"5319e7",{"name":2085,"color":2086},"discussion","538de2",21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.66904485,{"description":2093,"labels":2094,"number":2098,"owner":1985,"repository":2002,"state":2044,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### 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",[2095],{"name":2096,"color":2097},"question","d876e3",1740,"UCheckbox v-model as array","2025-03-31T08:02:40Z","https://github.com/nuxt/ui/issues/1740",0.67885923,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"O-PeTzCQ2YtHnmSaP3PfzYIMCtNqeoymKzw82Rjbfbk":-1},"/nuxt/ui/2923"]