\n```\nThis will help users operate data tables more efficiently.\n\n### Additional context\n\n_No response_",[2873,2874],{"name":2857,"color":2858},{"name":2860,"color":2861},2851,"UTable keyboard events","2024-12-09T05:42:48Z","https://github.com/nuxt/ui/issues/2851",0.723465,{"description":2881,"labels":2882,"number":2890,"owner":2863,"repository":2864,"state":2865,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[2883,2886,2889],{"name":2884,"color":2885},"bug","d73a4a",{"name":2887,"color":2888},"v3","49DCB8",{"name":2860,"color":2861},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.72390765,{"description":2896,"labels":2897,"number":2901,"owner":2863,"repository":2864,"state":2865,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, colorMode, build, runtimeConfig, app, lodash, vite, router, nitro\n- Runtime Modules: @pinia/nuxt@0.9.0, pinia-plugin-persistedstate/nuxt@4.2.0, @nuxt/test-utils/module@3.17.2, @vueuse/nuxt@11.3.0, nuxt-\ncountdown@1.2.0, nuxt-lodash@2.5.3, nuxt-monaco-editor@1.3.1, @nuxt/eslint@1.3.0, @nuxt/eslint@1.3.0, @nuxt/fonts@0.11.1, @nuxt/icon@1.12\n.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.6, @nuxt/test-utils@3.17.2, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fervent-ptolemy-6njy2z?workspaceId=ws_SZ9iN2xj3x4VbwxN8x8baL&embed=1&file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nYou cannot dynamically add/remove columns, top toggle should control the visibility of the Status column\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2898,2899,2900],{"name":2884,"color":2885},{"name":2887,"color":2888},{"name":2860,"color":2861},4024,"Dynamic table columns","2025-04-29T15:33:44Z","https://github.com/nuxt/ui/issues/4024",0.7262059,{"description":2907,"labels":2908,"number":2912,"owner":2863,"repository":2864,"state":2913,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### 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",[2909],{"name":2910,"color":2911},"question","d876e3",2667,"closed","I have no styling at the default UTable","2024-11-17T11:13:44Z","https://github.com/nuxt/ui/issues/2667",0.6898211,{"description":2919,"labels":2920,"number":2922,"owner":2863,"repository":2864,"state":2913,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### 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_",[2921],{"name":2857,"color":2858},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.69798625,{"description":2928,"labels":2929,"number":2933,"owner":2863,"repository":2864,"state":2913,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, runtimeConfig, ui\n- Runtime Modules: @nuxt/ui@3.1.0, @formkit/auto-animate/nuxt@0.8.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\n-\n\n### Description\n\nAfter upgrading from v3.0.2 to v3.1.0 I'm missing types for event binding directives and intellisense/automcomplete for attributes of all Nuxt UI components. Below I added a specific example for the Table component, but this happens to all components. I have removed node_modules, reinstalled, cleared the .nuxt and .output directories, and tried setting up a new project as well (using `npx nuxi init -t ui \u003Cmy-app>`).\n\nMissing types on event binding directives:\n\u003Cimg width=\"712\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b3bb862c-16aa-4deb-aa12-c07211034f9b\" />\n\nMissing autocomplete:\n\u003Cimg width=\"487\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8a851f0a-5894-41ae-8cdf-3f2f51d2ab52\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2930,2931,2932],{"name":2884,"color":2885},{"name":2887,"color":2888},{"name":2860,"color":2861},4029,"Where are all the types? v3.0.2 -> v3.1.0 upgrade","2025-04-30T12:20:42Z","https://github.com/nuxt/ui/issues/4029",0.70628583,{"description":2939,"labels":2940,"number":2942,"owner":2863,"repository":2864,"state":2913,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nHi,\n\nWould it be possible to add an export of all components ?\n\nSomething like:\n\n```js\nexport * from './components'\n```\n\n### Additional context\n\nI'm trying to display a form field according to its value type (ex: boolean => checkbox, number => range ...).\n\nSadly, it looks like in composition API, one cannot use string for `\u003Ccomponent>` `:is` prop.\n\n```vue\n\u003Ctemplate>\n \u003C!-- This doesn't work -->\n \u003Ccomponent :is=\"typeof value === 'boolean' ? 'u-checkbox' : 'u-input'\" />\n\u003C/template>\n```\n\nApparently, you have to pass the component itself, but I'm unable to import components from Nuxt UI:\n\n```vue\n\u003Cscript setup>\n// This doesn't work\nimport { UCheckbox, UInput } from '@nuxt/ui';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Ccomponent :is=\"typeof value === 'boolean' ? UCheckbox : UInput\" />\n\u003C/template>\n```\n\nI can use `v-if` as a workaround, but it forces me to duplicate a lot of props (class, listeners, model ...) on each component.",[2941],{"name":2857,"color":2858},2891,"Export of every components","2025-01-13T16:32:50Z","https://github.com/nuxt/ui/issues/2891",0.70908105,{"labels":2948,"number":2954,"owner":2863,"repository":2863,"state":2913,"title":2955,"updated_at":2956,"url":2957,"score":2958},[2949,2951],{"name":2857,"color":2950},"8DEF37",{"name":2952,"color":2953},"3.x","29bc7f",12962,"Type Support for Global Components (e.g. `\u003Cnuxt-link>`)","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12962",0.72106856,{"description":2960,"labels":2961,"number":2964,"owner":2863,"repository":2863,"state":2913,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the feature\n\nHey there! I'm really excited about the new `typedPages` feature. Great work on that one!\r\n\r\nI would like to create composable, for example a `useGetAppLocation`, that essentially returns a resolved url while adding a param that every url in my app needs. Example:\r\n\r\n```ts\r\n// props must be any because we don't have a type for it :/\r\nexport const useGetAppLocation = (props: any) => {\r\n\tconst router = useRouter()\r\n\tconst currentSpaceStore = useCurrentSpaceStore()\r\n\r\n\treturn router.resolve({\r\n\t\t...props,\r\n\t\tparams: {\r\n\t\t\t...props.params,\r\n\t\t\tspaceKey: currentSpaceStore.currentSpaceKey\r\n\t\t}\r\n\t})\r\n}\r\n```\r\n\r\nI would like to type this function, but as far as I can see nuxt doesn't export any types to do so. The `router.resolve()` uses `RouteNameMap`, `RouteLocationAsRelativeTyped`, `RouteLocationResolvedTyped ` and so on.\r\n\r\nIdeally, these types could be used in an application.\n\n### Additional information\n\n- [X] 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).",[2962,2963],{"name":2857,"color":2950},{"name":2952,"color":2953},21032,"`experimental.typedPages`: Export types to make usable in application","2023-05-24T12:19:35Z","https://github.com/nuxt/nuxt/issues/21032",0.721616,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYA0tVpyyeJFjLCdaas3O5mUqN7KQh_FnMoMtHNL562E":-1},"/nuxt/ui/2373"]