`\n\nit doesn't work that way\n\nI really ask for help!",[1984,1987],{"name":1985,"color":1986},"question","d876e3",{"name":1988,"color":1989},"v3","49DCB8",3098,"nuxt","ui","open","Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.6313374,{"description":1999,"labels":2000,"number":2010,"owner":1991,"repository":1992,"state":1993,"title":2011,"updated_at":2012,"url":2013,"score":2014},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.11.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.13.2\n- Nitro Version: 2.9.7\n- Package Manager: yarn@1.22.19\n- Builder: -\n- User Config: devtools, extends, modules, ssr, vite, runtimeConfig, ui, css, i18n, algolia, image, nitro, compatibilityDate\n- Runtime Modules: @nuxtjs/algolia@1.10.2, @nuxtjs/i18n@8.3.1, @pinia/nuxt@0.5.1, @nuxt/ui, @nuxt/image@1.7.0\n- Build Modules: -\n\n\n\n### Version\n\nNuxt UI pro 1.4.2\n\n### Reproduction\n\n-\n\n### Description\n\nOn Heroku, I randomly (~10%) get an error while building my project, indicating that NUXT_UI_PRO_LICENSE is not present.\nIt fix it but juste re-laucnhing the build a few seconds later\n\n```\n $ nuxt generate\n Nuxt 3.13.2 with Nitro 2.9.7\n ℹ Using Nitro server preset: static\n [nuxt:tailwindcss] ℹ Using default Tailwind CSS file\n ℹ Nuxt Icon server bundle mode is set to local\n ERROR Invalid NUXT_UI_PRO_LICENSE license key.\nPurchase Nuxt UI Pro at https://ui.nuxt.com/pro/pricing to build your app in production.\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2001,2004,2007],{"name":2002,"color":2003},"bug","d73a4a",{"name":2005,"color":2006},"pro","5BD3CB",{"name":2008,"color":2009},"triage","ffffff",3300,"Nuxt UI pro licensing failing randomly on Heroku","2025-02-19T16:07:14Z","https://github.com/nuxt/ui/issues/3300",0.6527982,{"description":2016,"labels":2017,"number":2021,"owner":1991,"repository":1992,"state":1993,"title":2022,"updated_at":2023,"url":2024,"score":2025},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@11.2.0\n- Builder: -\n- User Config: compatibilityDate, devtools, nitro, css, modules, vite\n- Runtime Modules: @nuxt/fonts@0.11.0, @nuxt/content@3.4.0, @nuxt/icon@1.11.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.5, @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex flex-col items-center justify-center gap-4 h-screen\">\n\n {{ state }}\n\n \u003Cdiv class=\"flex items-center gap-2\">\n \u003CUTree\n :items=\"gates\"\n label-key=\"label\"\n value-key=\"id\"\n v-model=\"state.gate\" \n >\n \u003C/UTree>\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n\n\n\u003Cscript\n lang=\"ts\"\n setup\n>\n\nimport type { FormSubmitEvent } from '@nuxt/ui'\n\ninterface Gate {\n id: number,\n label: string,\n uname: string\n}\n\ntype Schema = {\n gate: Gate\n}\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n gate: undefined,\n})\n\nconst gates = [{id:0, uname: null, label: \"unknown\"}, {id:1, uname: \"first-gate\", label: \"First\"}]\n\n\u003C/script>\n```\n\n### Description\n\nvalue-key points to id or missed.\n\nv-model type check points to id:number but there is full object.\n\n\n\n### Additional context\n\nHow to get full object here when bug fixed?\n\n### Logs\n\n```shell-script\n\n```",[2018,2019,2020],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2008,"color":2009},3762,"UTree value-key not working","2025-04-01T09:12:02Z","https://github.com/nuxt/ui/issues/3762",0.6587235,{"description":2027,"labels":2028,"number":2029,"owner":1991,"repository":2030,"state":1993,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Describe the feature\n\nI found, how to deploy nuxt 2 app into gcp app engine. But there is no doc about nuxt 3\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[],1764,"nuxt.com","deploy nuxt 3 on gcp appengine","2025-01-22T09:58:41Z","https://github.com/nuxt/nuxt.com/issues/1764",0.6597758,{"description":2036,"labels":2037,"number":2043,"owner":1991,"repository":1992,"state":1993,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### Description\n\nIt would be great to include these visuals directly in the component documentation pages, especially for layout components, to quickly understand their purpose at a glance.\n\n\n\nFor example, the visual could be added to the right side of the UPageHeader in the documentation. Clicking on the image could open a modal with a larger view for better readability.\n\n### Additional context\n\nlinked to this comment : https://github.com/nuxt/ui/issues/1289#issuecomment-2677068264",[2038,2041,2042],{"name":2039,"color":2040},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2008,"color":2009},3522,"Add visual to component documentation pages","2025-03-11T16:13:07Z","https://github.com/nuxt/ui/issues/3522",0.6723642,{"description":2049,"labels":2050,"number":2054,"owner":1991,"repository":1992,"state":1993,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### Description\n\nWhen adding `UButton` component with `ghost` or `link` variant inside a `UBanner` with `links` attribute, they remain displayed in black text, even if the banner has a dark background (e.g., primary color). Unlike the Banner close button, which has specific Tailwind classes that adapt it to dark mode (white text), these elements do not automatically adjust their colors.\n\n\n\n```html\n \u003CUBanner to=\"/guide-gouvernance-associative-crise\" icon=\"i-ph-books-duotone\" title=\"Guide Gouvernance Associative\" :actions=\"[{label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'ghost', size: 'md', trailingIcon: 'i-ph-arrow-right'}, {label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'link', size: 'md'}]\" close />\n```\n\nWould it be relevant to add a global attribute to components like Button, Badge, etc., to force their appearance in dark (or light) mode, regardless of the global setting? This would ensure better visual consistency when these elements are placed on a colored background (e.g., `UPageCTA` with `solid` variant).\n\n### Additional context\n\n_No response_",[2051,2052,2053],{"name":2039,"color":2040},{"name":1988,"color":1989},{"name":2008,"color":2009},3307,"Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.6733793,{"description":2060,"labels":2061,"number":2064,"owner":1991,"repository":1992,"state":2065,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Description\n\nsame as https://ui.nuxt.com/getting-started/installation#edge and https://ui.nuxt.com/pro/getting-started/installation#edge to test new components before release \n\n### Additional context\n\n_No response_",[2062,2063],{"name":2039,"color":2040},{"name":1988,"color":1989},2962,"closed","Create a edge version for `@nuxt/ui` and `@nuxt/ui-pro` v3","2025-01-25T13:12:16Z","https://github.com/nuxt/ui/issues/2962",0.5322453,{"description":2071,"labels":2072,"number":2075,"owner":1991,"repository":1992,"state":2065,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### Description\n\nHi,\n\nhere in the first form in nuxtui2\nhttps://ui.nuxt.com/components/form \nthe behaviour is that the input field is validated after the blur. If there is an error and I correct it, the error is fixed immediately.\n\nIn v3 the behaviour is different. I have seen the prop validateOn so I can change it to blur, but not like first onBlur and then onInput like in v2.\n\nbest,\ngregor",[2073,2074],{"name":2002,"color":2003},{"name":1988,"color":1989},3006,"How can I get the same form validation behaviour as in v2?","2025-01-06T17:48:11Z","https://github.com/nuxt/ui/issues/3006",0.6193087,{"description":2081,"labels":2082,"number":2083,"owner":1991,"repository":2030,"state":2065,"title":2084,"updated_at":2085,"url":2086,"score":2087},"After using `pnpm update` to upgrade vue to 3.4.3, the console throws a lot of `Hydration mismatch`. If I am using vue 3.3.13, no `Hydration mismatch` warnings will be thrown.\r\n\r\n\u003Cimg width=\"1402\" alt=\"SCR-20240103-qagg\" src=\"https://github.com/nuxt/nuxt.com/assets/133459587/188ac1c4-e19a-4570-a5d0-4863c92a7bda\">\r\n",[],1467,"About vue@3.4.3 causing hydration mismatch","2024-05-03T00:34:36Z","https://github.com/nuxt/nuxt.com/issues/1467",0.6241872,{"description":2089,"labels":2090,"number":2093,"owner":1991,"repository":1992,"state":2065,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Description\n\nFor custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties `touched` and `dirty` exposed.\n\n- `Touched` (opposite of `untouched`): A field is considered touched when a user has focused it OR changed it's value\n- `Dirty` (opposite of `pristine`): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.\n\nYou can currently work around most of these by using a computed on the exposed `errors` ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.\n\n### Additional context\n\n_No response_",[2091,2092],{"name":2039,"color":2040},{"name":1988,"color":1989},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.62934,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"tPFKMHgqHhErVuBxyhlyR115shtOyBc7ZPSKsydTRZE":-1},"/nuxt/ui/2322"]