\n\u003CUSkeleton class=\"h-32\" :ui=\"{ base: 'rounded-xl' }\" />\n```\n\nResults in:\n\n```\n\u003Cdiv class=\"animate-pulse rounded-md bg-elevated h-32\">\u003C/div>\n```\n",[3203,3204],{"name":3189,"color":3190},{"name":3192,"color":3193},4691,"closed","USkeleton: `:ui` prop has no effect","2025-08-10T16:41:52Z","https://github.com/nuxt/ui/issues/4691",0.71541625,{"description":3212,"labels":3213,"number":3223,"owner":3178,"repository":3179,"state":3206,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Description\n\nIs there a way to add custom props to a component for styling—similar to how variant works for buttons? I’d like to add variant support to FormField, but currently, it only supports size.\n\nMy main goal is to allow styling of components provided by my Nuxt module. Ideally, I want to define variants and extra props via app.config.ts. An alternative approach I'm thinking of is to offer per-component config options, similar to Nuxt UI, but managed separately from its config.",[3214,3217,3218,3221],{"name":3215,"color":3216},"question","d876e3",{"name":3192,"color":3193},{"name":3219,"color":3220},"closed-by-bot","ededed",{"name":3222,"color":3220},"stale",4148,"Additional props like variants for styling","2025-08-20T02:08:47Z","https://github.com/nuxt/ui/issues/4148",0.7178378,{"description":3229,"labels":3230,"number":3233,"owner":3178,"repository":3179,"state":3206,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Description\n\nHi,\n\nBeing able to override the **non-slot** properties of the tv theme using the ui prop would be very handy.\n\nSometimes you don't want to override globally but just want a slightly different variation of a component. When trying to restyle variations it becomes quite tricky when you cant override anything other than the slots.\n\neg. if you wanted to override compoundVariants the only choice is to do it globally, which naturally effects all uses of that component.\n\nA use case here is the UNavigationMenu. Accurately restyling hover effects etc is tricky without being able to override the whole tv object.\n\nI was also thinking it would be nice to be able to define your own theme directory where you could define component tv objects which either replace or merge with the Nuxt ui versions.\n\nThanks\nLee\n\n### Additional context\n\n_No response_",[3231,3232],{"name":3172,"color":3173},{"name":3192,"color":3193},3382,"Add ability to override entire tv object from ui prop","2025-05-23T13:04:10Z","https://github.com/nuxt/ui/issues/3382",0.7287466,{"description":3239,"labels":3240,"number":3246,"owner":3178,"repository":3178,"state":3206,"title":3247,"updated_at":3248,"url":3249,"score":3250},"Hello,\r\n\r\nWhen I add a class on \u003Cnuxt /> tag in a template, it's added rightly on SSR, but not when rendered with client.\r\n\r\nPoC : https://glitch.com/edit/#!/nuxt-issue-672\r\n\r\nIn this PoC, on the index page, when about is rendered with server, we can see red background, not when it's rendered by client.\r\n\r\nThanks,\r\nGaël\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c581\">#c581\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3241,3243],{"name":3172,"color":3242},"8DEF37",{"name":3244,"color":3245},"2.x","d4c5f9",672,"Class on \u003Cnuxt /> tag","2023-01-18T15:39:39Z","https://github.com/nuxt/nuxt/issues/672",0.7329078,{"description":3252,"labels":3253,"number":3255,"owner":3178,"repository":3179,"state":3206,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\ni add the default table but have another styling.\nhow can i fix this? \n\n` \u003CUTable\n v-model:expand=\"expand\"\n class=\"w-full\"\n :loading-state=\"{ icon: 'i-heroicons-arrow-path-20-solid', label: 'Loading...' }\"\n :progress=\"{ color: 'primary', animation: 'carousel' }\"\n :rows=\"people\"\n :columns=\"columns\"\n >`\n\n",[3254],{"name":3215,"color":3216},2667,"I have no styling at the default UTable","2024-11-17T11:13:44Z","https://github.com/nuxt/ui/issues/2667",0.7341883,{"description":3261,"labels":3262,"number":3264,"owner":3178,"repository":3179,"state":3206,"title":3265,"updated_at":3266,"url":3267,"score":3268},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nHow can add a class to the \"selectable\" column? Other columns I can use the `class` attribute (https://ui.nuxt.com/components/table#columns) for the column, but for the automatically showing \"selectable\" column, there's no such way to customize it\n\n### Additional context\n\n_No response_",[3263],{"name":3172,"color":3173},2377,"Ability to add custom column data (specifically class) to automatically showing selectable column","2024-11-12T17:12:38Z","https://github.com/nuxt/ui/issues/2377",0.7348683,{"labels":3270,"number":3273,"owner":3178,"repository":3178,"state":3206,"title":3274,"updated_at":3275,"url":3276,"score":3277},[3271,3272],{"name":3172,"color":3242},{"name":3244,"color":3245},6546,"@nuxtjs/font-awesome needs to be updated to version 5","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6546",0.7385484,{"description":3279,"labels":3280,"number":3283,"owner":3178,"repository":3179,"state":3206,"title":3284,"updated_at":3285,"url":3286,"score":3287},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nTo simplify customization and ensure visual consistency across projects, it would be useful to add a configuration option to define `defaultVariants` globally or for specific component types. These variants could include default size, color, and variant properties for all components or specific ones like buttons, button groups, and form fields. \n\n### Proposal: \n1. Introduce a `defaultVariants` field in the Nuxt configuration to: \n - Define **global variants** (applied to all components). \n - Define **component-specific variants** (e.g., for buttons, forms, etc.). \n\n### Example Implementation: \nIn the Nuxt configuration file: \n```javascript\nexport default defineNuxtConfig({\n ui: {\n defaultVariants: {\n // Global variants\n global: {\n size: 'lg',\n color: 'neutral',\n },\n // Button and ButtonGroup variants\n button: {\n size: 'md',\n color: 'primary',\n variant: 'solid',\n },\n // Form input, select, … variants\n form: {\n size: 'lg',\n color: 'neutral',\n variant: 'outlined',\n },\n },\n },\n});\n``` \n\n### Usage: \nThe defined `defaultVariants` would automatically be applied to all components without the need to explicitly specify these props in templates. Props provided in the template would always take precedence over the ones defined in the configuration. \n\n### Benefits: \n- Reduces repetition in templates. \n- Enhances visual consistency across the project. \n- Flexibility to customize globally or per component type. \n- Easy adoption with prop priority management. \n\n### Expected Impact: \nThis feature would add flexibility while making the integration of `@nuxt/ui` faster and more intuitive by allowing consistent and customized variants to be managed at various levels of the project. \n\nThanks for your continued work on `@nuxt/ui`, which remains an essential tool for building modern and performant interfaces. \n\n### Additional context\n\n_No response_",[3281,3282],{"name":3172,"color":3173},{"name":3192,"color":3193},2934,"Add `defaultVariants` option to define global or component-specific size, variant, and color settings","2025-07-09T12:37:51Z","https://github.com/nuxt/ui/issues/2934",0.74280864,["Reactive",3289],{},["Set"],["ShallowReactive",3292],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTKu2FonuUsPQbHFzJ5qfhru2unimVwB-qtoIGPh0rFQ":-1},"/nuxt/ui/4807"]