\n```\n\n---\nI checked the latest documentation, and the examples of UTable regarding column display control seem to have no effect, such as: https://ui3.nuxt.dev/components/table#with-column-visibility.\n\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3075,3076],{"name":3064,"color":3065},{"name":3049,"color":3050},2874,"The update of the columns property will not trigger an update of the UTable component","2025-01-25T13:12:40Z","https://github.com/nuxt/ui/issues/2874",0.67920494,{"description":3083,"labels":3084,"number":3089,"owner":3021,"repository":3021,"state":3037,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.9.0`\r\n- Nuxt Version: `3.0.0-rc.12-27768618.05fd222`\r\n- Nitro Version: `0.6.0-27768582.4603279`\r\n- Package Manager: `pnpm@7.13.5`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `runtimeConfig`, `css`, `pageTransition`, `nitro`, `modules`, `schemaOrg`, `unocss`, `umami`, `content`\r\n- Runtime Modules: `@nuxt/image-edge@1.0.0-27768165.4b0219a`, `@nuxt/content@2.1.1`, `@vueuse/nuxt@9.3.1`, `@unocss/nuxt@0.45.30`, `@formkit/nuxt@1.0.0-beta.11`, `nuxt-swiper@0.1.6`, `nuxt-umami@1.1.0`, `nuxt-schema-org@1.1.0-beta.5`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n> **Note**\r\n> I will add reproduction but for now I will have to decouple my current project that in private.\r\n\r\nIn the meantime I will try to re-produce this.\r\n\r\nThanks \r\n\r\n### Describe the bug\r\n\r\nUpstream bug: https://github.com/vueuse/head/issues/142\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell\r\nUpstream bug: https://github.com/vueuse/head/issues/142\r\n```\r\n",[3085,3088],{"name":3086,"color":3087},"3.x","29bc7f",{"name":3031,"color":3032},15190,"`@vueuse/head` nuxt@3.0.0-rc.12 - upstream bug","2023-01-19T17:45:58Z","https://github.com/nuxt/nuxt/issues/15190",0.679517,{"description":3095,"labels":3096,"number":3097,"owner":3021,"repository":3022,"state":3037,"title":3098,"updated_at":3099,"url":3100,"score":3101},"On the 'Enterprise Jobs' page, location badges were closely together on mobile screens. I removed the `mr-3` class from the badge element and placed the badges inside a parent `\u003Cdiv>` with the classes` flex`, `flex-wrap`, and `gap-3` Now it won't stick together and will look good on mobile devices.\r\n\r\n| **BEFORE** | **AFTER** | \r\n|-------- | ------ | \r\n|  |  |\r\n\r\n\r\n\r\n\n```[tasklist]\n### Tasks\n```\n",[],1403,"Spacing issue with Location badges on 'Enterprise Jobs' page for mobile screens","2024-09-19T19:38:43Z","https://github.com/nuxt/nuxt.com/issues/1403",0.68003565,{"description":3103,"labels":3104,"number":3109,"owner":3021,"repository":3055,"state":3037,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Description\n\nBefore using `nuxt ui`, I briefly skimmed through the repository and found an already closed issue: [3018](https://github.com/nuxt/ui/issues/3018)\n\nThe error and solution mentioned in this issue (the [v2 documentation](https://ui.nuxt.com/getting-started/installation) indeed did not mention the solution) can actually be resolved by adding `tailwindcss@next` to the `peerDependencies` section in the `package.json` file.\n\nThis is because when [nuxi module add](https://github.com/nuxt/cli/blob/1afc06e8d08ea781fc5fede343de8d68865c2b4e/packages/nuxi/src/commands/module/add.ts#L134) installs a module, it not only installs the module itself but also scans the module package's `peerDependencies`.\n\nFor example, when using `nuxi module add pinia`, since `@pinia/nuxt` has `pinia` listed in its `peerDependencies` in the [package.json](https://github.com/vuejs/pinia/blob/3b21e08b6a068d18112b915b83f702fb5504ab73/packages/nuxt/package.json#L51C4-L51C20), both `@pinia/nuxt` and `pinia` will be automatically installed during the module installation.\n\nIf there are dependencies in `peerDependencies` that you do not want `nuxi module` to install automatically, you can use `peerDependenciesMeta` to ignore them, for [example](https://github.com/atinux/nuxt-auth-utils/blob/6b61b8888e3b3c6f60fd5ff767b7f0aa6cf09fc9/package.json#L57):\n\n```\n\"peerDependenciesMeta\": {\n \"pinia\": {\n \"optional\": true\n }\n },\n```\n\nTherefore, Nuxt UI can specify `tailwindcss@next` in the `peerDependencies` of `package.json`, ensuring Tailwind CSS is automatically installed when the Nuxt UI module is installed.\n\nThis solution applies to both v3 and v2.\n\n> PS: I noticed `typescript` in the `peerDependencies` of the v3 package.json. Is this a necessary dependency similar to `tailwindcss`? If not, after adding tailwindcss, perhaps `peerDependenciesMeta` could be used to ignore it.",[3105,3108],{"name":3106,"color":3107},"question","d876e3",{"name":3049,"color":3050},3349,"Add \"tailwindcss@next\" to the \"peerDependencies\" section in the package.json file.","2025-02-21T17:05:10Z","https://github.com/nuxt/ui/issues/3349",0.6816711,{"description":3115,"labels":3116,"number":3120,"owner":3021,"repository":3121,"state":3037,"title":3122,"updated_at":3123,"url":3124,"score":3125},"### Environment\n\nWorking directory: /home/projects/jvmibwmjx.github\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-mmtufx?file=app.vue\n\n### Describe the bug\n\nLet's say there is a root component which I want to mount using `@nuxt/test-utils`'s `mountSuspended()` API. If this component\r\n\r\n- uses `\u003Cscript setup>`\r\n- imports composable API from Nuxt `#import` (i.e. `useRouter`, `useRoute`, ...)\r\n\r\nit makes an error below and breaks entire test.\r\n\r\n```bash\r\nstdout | createSuspenseBoundary (/home/projects/jvmibwmjx.github/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1451:43)\r\n\u003CSuspense> is an experimental feature and its API will likely change.\r\n\r\nstderr | warn$1 (/home/projects/jvmibwmjx.github/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:50:13)\r\n[Vue warn]: Cannot mutate \u003Cscript setup> binding \"useRouter\" from Options API. \r\n at \u003CMountSuspendedComponent > \r\n at \u003CMountSuspendedHelper> \r\n at \u003CAnonymous ref=\"VTU_COMPONENT\" > \r\n at \u003CVTUROOT>\r\n[Vue warn]: Unhandled error during execution of render function \r\n at \u003CMountSuspendedComponent > \r\n at \u003CMountSuspendedHelper> \r\n at \u003CAnonymous ref=\"VTU_COMPONENT\" > \r\n at \u003CVTUROOT>\r\n```\r\n\r\nOnly if the root component meets the condition above, the issue occurs. As you see in the reproduction, if you use `#imports` and `\u003Cscript setup>` in child elements it work fine.\r\n\r\nThe app itself is built and works fine if I run it.\r\n\r\nYou can reproduce the issue with the repository link above.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3117,3118],{"name":3064,"color":3065},{"name":3031,"color":3119},"5D08F5",871,"test-utils","Using `mountSuspended()` with a component using `\u003Cscript setup>` and `#import` makes an error","2025-01-30T17:30:54Z","https://github.com/nuxt/test-utils/issues/871",0.6873373,{"description":3127,"labels":3128,"number":3131,"owner":3021,"repository":3055,"state":3037,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nI've noticed that links (\\\u003Ca\\> tags) created with `UButton` contain a lot of unnecessary styling related to the button itself, disabled and enabled state. Given that for anchors there is no `disabled` property in the HTML specification, this means that out of the following styles:\n```\nrounded-[calc(var(--ui-radius)*1.5)] font-medium inline-flex items-center focus:outline-none transition-colors px-2.5 py-1.5 text-sm gap-1.5 ring ring-inset ring-[var(--ui-primary)]/50 text-[var(--ui-primary)] hover:bg-[var(--ui-primary)]/10 focus-visible:ring-2 focus-visible:ring-[var(--ui-primary)]\n```\n\nAt the very least, these can be removed:\n\n```\ndisabled:cursor-not-allowed aria-disabled:cursor-not-allowed disabled:opacity-75 aria-disabled:opacity-75 disabled:bg-transparent aria-disabled:bg-transparent dark:disabled:bg-transparent dark:aria-disabled:bg-transparent\n```\n\nThis is quite a reduction in classes and can make a moderate difference in total page size and even web vitals scores, especially if there are a lot of links on the page created with `UButton` (which is very likely given the customization UButton provides with icons, variants, colors, and more)\n\nIn order to make this work, the classes that rely on disabled state would likely need to be extracted into a separate place in the theme, which tailwind-variants will then need to merge if there is no `to` property present.\n\nYou might be asking why, given that technically people can rely on it to prevent navigation until a certain condition. But the answer to that is that restricting links like that is generally bad practice and can be circumvented pretty easily. It's not meant to be a security feature and it also lacks in terms of functional purpose.\n\nI'll check to see what I can do about it, but I thought sharing it here would be more beneficial in case someone will be faster than me in preparing a PR for this =)",[3129,3130],{"name":3106,"color":3107},{"name":3049,"color":3050},2907,"[Performance improvement opportunity]: remove disabled-dependent classes on links created with `UButton`","2025-01-13T22:45:37Z","https://github.com/nuxt/ui/issues/2907",0.6874631,["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDTiHBY8Z0WBQtWRpYvCJ7exNkEcREVR_6dMvCdrAwNQ":-1},"/nuxt/ui/3898"]