\n4. add items to array \n \u003Ctempalte>\n \u003CUButton label=\"add\" @click=\"addItem\" />\n\n\n \u003CScript setup>\n const addItem = () => { items.value.push(\"Done\")}\n5. check table rows\n\n\nActual Result\nnew item is added to array but not in table until nex hot reload\n\nExpected result\nnew item should be added to table rows, as NuxUI V2\n\n\nnote: same issue adding colums props\n\n### Description\n\nUTable is not showing new items added to reactive array used for data until nex hot module reload\n\n\nhttps://codesandbox.io/p/devbox/fancy-hill-5fr65h?workspaceId=ws_Xcg6XEDPVvQDQh4Bj2yVGA\n\n\n### Additional context\n\n\u003Ctemplate>\n \u003CUContainer>\n \u003CUButton label=\"add\" @click=\"addItem\" />\n \u003CUTable :data= \"items\"/>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst items = ref([\"Backlog\", \"Todo\", \"In Progress\" ]);\n\nconst addItem = () => {\n // pushing done to items array is no updated in table rows\n items.value.push(\"Done\")\n console.log(items.value)\n\n // Work arrond.\n // create a new arry reference an then assing it to items\n // this way new row is being added to table\n // const arr = items.value\n // items.value = [...arr]\n }\n\u003C/script>\n\n### Logs\n\n```shell-script\n\n```",[3034,3037,3038],{"name":3035,"color":3036},"bug","d73a4a",{"name":3021,"color":3022},{"name":3039,"color":3040},"triage","ffffff",3732,"[Table] new item added to array is not rendered in table","2025-03-30T08:41:27Z","https://github.com/nuxt/ui/issues/3732",0.73031276,{"description":3047,"labels":3048,"number":3051,"owner":3024,"repository":3025,"state":3026,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.11.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8, @nuxtjs/html-validator@1.8.2, @nuxt/image@1.8.1, @nuxt/eslint@0.6.1, @nuxtjs/seo@2.0.0-rc.23\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"@nuxt/ui\": \"3.0.0-alpha.8\",\n\n### Reproduction\n\n\u003C!-- layouts/default.vue -->\n\u003Ctemplate>\n \u003Cdiv class=\"container mx-auto\">\n \u003Cu-breadcrumb :items=\"items \" />\n \u003Cslot>\u003C/slot>\n \u003C/div>\n\u003C/template>\n\n\n\u003Cscript lang=\"ts\" setup>\nimport { useRoute } from 'vue-router';\n\nconst route = useRoute();\nconst items = useBreadcrumbItems({\n schemaOrg: true,\n});\n\u003C/script>\n\n\n### Description\n\nthis will render the breadcrumbs in a \u003Cdiv> with an aria-label, which is a violation of this rule: https://html-validate.org/rules/aria-label-misuse.html\n\n- Rule ID: aria-label-misuse\n- Category: Accessibility\n- Standards: WCAG 2.2 (A)WCAG 2.1 (A)WCAG 2.0 (A)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n ERROR HTML validation errors found for /song/justice-genesis-1\n\ninline\n 129:21990 error \"aria-label\" cannot be used on this element aria-label-misuse\n\n✖ 1 problem (1 error, 0 warnings)\n\nMore information:\n https://html-validate.org/rules/aria-label-misuse.html\n\n```",[3049,3050],{"name":3035,"color":3036},{"name":3021,"color":3022},2649,"breadcrumb HTML validation errors","2024-11-15T08:53:33Z","https://github.com/nuxt/ui/issues/2649",0.7309538,{"description":3057,"labels":3058,"number":3063,"owner":3024,"repository":3025,"state":3026,"title":3064,"updated_at":3065,"url":3066,"score":3067},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.13.2\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: modules, typescript\r\n- Runtime Modules: @nuxt/ui@2.18.6\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\n2.18.6\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-itcrga?file=app.config.ts\r\n\r\n> Type '\"white\"' is not assignable to type '\"primary\"'. ts(2322)\r\n\r\n### Description\r\n\r\n`primary` is the only possible value for colours in the default config of a lot of components. Issue appeared with 2.18.x\r\nAlso noticed a similar issue on other configs, like `variant` for buttons\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3059,3060],{"name":3035,"color":3036},{"name":3061,"color":3062},"duplicate","cfd3d7",2241,"Type issue with colors/variant in app.config.ts","2024-10-06T18:03:19Z","https://github.com/nuxt/ui/issues/2241",0.73282826,{"description":3069,"labels":3070,"number":3076,"owner":3024,"repository":3025,"state":3026,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Description\n\n\n## 🔧 Current Behavior\n\nThe `deferInputValidation` parameter in `useFormField` is currently hardcoded in the `Input` component:\n\n```ts\nconst { emitFormBlur, emitFormInput, /* ... */ } = useFormField\u003CInputProps>(props, { \n deferInputValidation: false // Hardcoded\n})\n```\n\nThis limits flexibility, as consumers of the `Input` component cannot control validation timing behavior (e.g., validate on blur vs. validate on input).\n\n## ✅ Proposed Solution\n\nMake `deferInputValidation` configurable via a component prop:\n\n1. **Pass dynamic value to `useFormField`:**\n\n```ts\nuseFormField\u003CInputProps>(props, {\n deferInputValidation: props.deferInputValidation\n})\n```\n\n2. **Update the component props interface:**\n\n```ts\ndeferInputValidation?: boolean\n```\n\n---\n\n## 💡 Use Cases\n\n- **Delayed validation** for complex, interdependent form fields \n- **Immediate validation** for sensitive or critical fields \n- Flexibility for UX patterns like **\"validate-on-blur\"** or **\"validate-as-you-type\"**\n\n---\n\n## 🔁 Alternatives Considered\n\n- **Wrapper Component**: Adds unnecessary complexity \n- **Global Form-Level Config**: Less flexible than per-field control\n\n---\n\n## 🧪 Testing Impact\n\n- Covered by existing validation tests with both `true` and `false` cases\n\n---\n\n## 📚 Documentation\n\nRequires updates to:\n\n- Component prop API \n- Form validation best practices\n\n---\n\n## ⚙️ Why This Matters\n\nThis change supports **Inversion of Control** — empowering component consumers to control validation timing based on specific UX needs.\n```\n\n### Additional context\n\n_No response_",[3071,3074,3075],{"name":3072,"color":3073},"enhancement","a2eeef",{"name":3021,"color":3022},{"name":3039,"color":3040},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.7339245,{"description":3082,"labels":3083,"number":3090,"owner":3024,"repository":3025,"state":3026,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.19.0\n- Nuxt Version: -\n- CLI Version: 3.23.1\n- Nitro Version: -\n- Package Manager: pnpm@10.7.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nfreshly pulled official starter template using\n```bash\nnpx giget@latest gh:nuxt-ui-pro/starter-vue . --force\n```\ncleaned components.d.ts / deleted it\nit has been recreated: but missing ALL nuxtui components:\n\n```js\n/* eslint-disable */\n// @ts-nocheck\n// Generated by unplugin-vue-components\n// Read more: https://github.com/vuejs/core/pull/3399\n// biome-ignore lint: disable\nexport {}\n\n/* prettier-ignore */\ndeclare module 'vue' {\n export interface GlobalComponents {\n LogoPro: typeof import('./src/components/LogoPro.vue')['default']\n RouterLink: typeof import('vue-router')['RouterLink']\n RouterView: typeof import('vue-router')['RouterView']\n }\n}\n```\n\n### Description\n\nThe components.d.ts file generated by `unplugin-vue-components` is incomplete.\n\n### Additional context\n\n```js\nimport { defineConfig } from 'vite'\nimport vue from '@vitejs/plugin-vue'\nimport uiPro from '@nuxt/ui-pro/vite'\n\n// https://vitejs.dev/config/\nexport default defineConfig({\n plugins: [\n vue(),\n uiPro({\n ui: {\n colors: {\n primary: 'green',\n neutral: 'slate'\n }\n },\n prefix: 'U'\n })\n ]\n})\n```\n\n### Logs\n\n```shell-script\n\n```",[3084,3085,3088,3089],{"name":3035,"color":3036},{"name":3086,"color":3087},"needs reproduction","CB47CF",{"name":3021,"color":3022},{"name":3039,"color":3040},3753,"unplugin components.d.ts not working","2025-03-31T13:04:11Z","https://github.com/nuxt/ui/issues/3753",0.73674345,{"description":3096,"labels":3097,"number":3098,"owner":3024,"repository":3099,"state":3026,"title":3100,"updated_at":3101,"url":3102,"score":3103},"- [x] Colors & Fonts\n- [x] Landing page (Home)\n- [x] Showcase categories/hero\n- [x] Modules categories/hero\n- [x] Blog categories/hero\n- [x] Support hero/content",[],1305,"nuxt.com","Marketing Update","2023-07-04T10:00:31Z","https://github.com/nuxt/nuxt.com/issues/1305",0.74564445,{"description":3105,"labels":3106,"number":3109,"owner":3024,"repository":3099,"state":3026,"title":3110,"updated_at":3111,"url":3112,"score":3113},"- [x] Move Revue contacts\n- [x] Subscribe form to contact Sendgrid API",[3107],{"name":3072,"color":3108},"1ad6ff",1104,"Migrate newsletter to SendGrid","2023-01-10T15:04:54Z","https://github.com/nuxt/nuxt.com/issues/1104",0.74581224,{"description":3115,"labels":3116,"number":3120,"owner":3024,"repository":3025,"state":3026,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.4\r\n- Builder: -\r\n- User Config: compatibilityDate, runtimeConfig, experimental, router, i18n, devServer, devtools, app, components, modules, vue, tailwindcss, image, ui, nitro, storyblok, algolia, colorMode, hooks\r\n- Runtime Modules: @nuxt/devtools@1.4.1, @nuxt/image@1.8.0, @nuxt/ui@2.18.4, @nuxtjs/i18n@8.5.1, @pinia/nuxt@0.5.4, @storyblok/nuxt@6.0.10, @vueuse/nuxt@11.0.3, nuxt-og-image@3.0.0-rc.66, @stefanobartoletti/nuxt-social-share@1.0.1\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-y5b7nb?file=app.vue\n\n### Description\n\nWhen using the button component with color 'white' and variant 'link', 'outline' or 'soft' invalid Tailwind color classes are generated, e.g. 'text-white-500'. It should be 'text-white'.\r\n\r\ntext-white-500 hover:text-white-600 disabled:text-white-500 dark:text-white-400 dark:hover:text-white-500 dark:disabled:text-white-400 focus-visible:ring-inset focus-visible:ring-white-500 dark:focus-visible:ring-white-400\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3117],{"name":3118,"color":3119},"question","d876e3",2109,"White link, outline and soft buttons generate wrong Tailwind classes, e.g. 'text-white-500'","2024-09-06T13:10:25Z","https://github.com/nuxt/ui/issues/2109",0.7529508,{"description":3126,"labels":3127,"number":3130,"owner":3024,"repository":3025,"state":3026,"title":3131,"updated_at":3132,"url":3133,"score":3134},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3128,3129],{"name":3035,"color":3036},{"name":3021,"color":3022},3220,"Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3220",0.75548166,["Reactive",3136],{},["Set"],["ShallowReactive",3139],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmdQBKScMldz2cVj7GUP7ft8UJiuCkmDJv4uYsmKp-Zw":-1},"/nuxt/nuxt.com/1228"]