\n\n \u003C!-- \u003CUAccordion :items=\"items\" /> -->\n\n \u003CUDrawer id=\"drawer\">\n \u003CUButton label=\"Open\" color=\"surface\" variant=\"solid\" />\n \u003Ctemplate #content>\n \u003CBaseUiPlaceholder class=\"h-48 m-4\" />\n \u003C/template>\n \u003C/UDrawer>\n```\n\nIf we use Accordion or Drawer (as mentioned in above code), we get 500 Error and app crashes. \n\n\n\nIf we comment out the Accordion and Drawer, no error comes, and app works nicely. \n\n\n\nSee: No error if we don't use the error-causing components. \n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3050,3051],{"name":3019,"color":3020},{"name":3022,"color":3023},2769,"closed","[v3] Error `$setup.useId is not a function` in Accordion, Drawer, etc.","2024-11-26T13:44:15Z","https://github.com/nuxt/ui/issues/2769",0.6980986,{"description":3059,"labels":3060,"number":3065,"owner":3028,"repository":3029,"state":3053,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Description\n\nHello, I just wanted to overwrite shadow-sm with another shadow in the card root slot.\nBut I failed to do so. I tried the :ui way and the app.config.ts way but in both cases the new class \"shadow-card\" ended up BEHIND \"shadow-sm\".\n\n```\n card: {\n slots: {\n root: \"shadow-card\",\n },\n },\n```\n\nSo shadow-card always gets overwritten by shadow-sm cause the code always ends up like this:\n```\n\u003Cdiv class=\"bg-[var(--ui-bg)] ring ring-[var(--ui-border)] divide-y divide-[var(--ui-border)] rounded-[calc(var(--ui-radius)*2)] shadow-sm shadow-card\">\n```\n\nso how can I overwrite shadow-sm here?",[3061,3064],{"name":3062,"color":3063},"question","d876e3",{"name":3022,"color":3023},2936,"Overwrite css classes of slots","2025-01-08T16:26:22Z","https://github.com/nuxt/ui/issues/2936",0.69978607,{"description":3071,"labels":3072,"number":3073,"owner":3028,"repository":3042,"state":3053,"title":3074,"updated_at":3075,"url":3076,"score":3077},"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.7007829,{"description":3079,"labels":3080,"number":3082,"owner":3028,"repository":3029,"state":3053,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Description\n\nHi, using the UTable with Expanded feature is it possible to apply a style to the Expand column ??? I can see how to do this for columns I add but not the expanded column.\r\nAlso is it possible to change the default so the expanded is open by default? Or to change this in the script section?\r\n\r\nThanks I was unable to find answers in the docs.",[3081],{"name":3062,"color":3063},2244,"UTable Expandable questions?","2024-11-05T14:52:12Z","https://github.com/nuxt/ui/issues/2244",0.70298046,{"description":3088,"labels":3089,"number":3093,"owner":3028,"repository":3029,"state":3053,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### 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_",[3090,3092],{"name":3039,"color":3091},"a2eeef",{"name":3022,"color":3023},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.70419025,{"description":3099,"labels":3100,"number":3104,"owner":3028,"repository":3042,"state":3053,"title":3105,"updated_at":3106,"url":3107,"score":3108},"- List modules\n- Install a module\n\nLink it in the modules section in concepts.\n",[3101],{"name":3102,"color":3103},"documentation","9DE2BA",1369,"[API][Commands] Add `modules` ","2023-12-18T12:00:05Z","https://github.com/nuxt/nuxt.com/issues/1369",0.7047985,{"description":3110,"labels":3111,"number":3113,"owner":3028,"repository":3029,"state":3053,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Environment\r\n\r\nnewest\r\n\r\n### Version\r\n\r\n^2.13.0\r\n\r\n### Reproduction\r\n\r\n`\u003CUTabs :ui=\"{strategy: 'override'}\">`\r\n\r\n### Description\r\n\r\nMake a UTabs component with an ui prop and set strategy as a string. Typescript will complain but it will render as intended\r\n\r\nTypes of property 'strategy' are incompatible.\r\nType 'string' is not assignable to type 'Strategy | undefined'\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3112],{"name":3019,"color":3020},2268,":ui prop typescript error with 'strategy' as a string","2024-09-30T09:51:02Z","https://github.com/nuxt/ui/issues/2268",0.7081024,{"description":3119,"labels":3120,"number":3126,"owner":3028,"repository":3029,"state":3053,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.18.2\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: pnpm@10.8.0\n- Builder: -\n- User Config: extends, modules, ssr, site, runtimeConfig, alias, sourcemap, future, features, nitro, hub, eslint, i18n, sentry\n- Runtime Modules: @sentry/nuxt/module@9.12.0 @compodium/nuxt@0.1.0-beta.8, @nuxt/test-utils/module@3.17.2, @vueuse/nuxt@13.1.0, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.2.0, @nuxt/ui@3.0.2, reka-ui/nuxt@2.2.0, @nuxt/image@1.10.0, @formkit/auto-animate/nuxt@0.8.2, motion-v/nuxt@1.0.0-beta.2, nuxt-svgo@4.0.17, @nuxt/eslint@1.3.0, nuxt-llms@0.1.2, nuxt-security@2.2.0, @nuxtjs/seo@3.0.2, @nuxtjs/i18n@9.5.3, nuxt-auth-utils@0.5.19, @nuxt/scripts@0.11.5, nuxt-delay-hydration@1.3.8\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.2\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/navigation-menu#arrow\n\n### Description\n\nYou can even reproduce this in the current demo page, the arrow is not moving, or for some reason it glitches, this doesn't happen with the Reka components\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3121,3122,3123],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3124,"color":3125},"reka-ui","56d799",3907,"NavigationMenu arrow not moving","2025-05-15T14:41:00Z","https://github.com/nuxt/ui/issues/3907",0.7101782,["Reactive",3132],{},["Set"],["ShallowReactive",3135],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9a6TgToM58ZOAzz2sFkTlXEoHQc0exlfz_Lvvm8IXAc":-1},"/nuxt/ui/3652"]