\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```",[2932,2933],{"name":2914,"color":2915},{"name":2917,"color":2918},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.67270124,{"description":2940,"labels":2941,"number":2946,"owner":2903,"repository":2923,"state":2924,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2942,2945],{"name":2943,"color":2944},"question","d876e3",{"name":2917,"color":2918},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.6734383,{"description":2952,"labels":2953,"number":2956,"owner":2903,"repository":2923,"state":2924,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[2954,2955],{"name":2943,"color":2944},{"name":2917,"color":2918},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.67588514,{"description":2962,"labels":2963,"number":2973,"owner":2903,"repository":2903,"state":2924,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.15.1\n- Nuxt Version: 3.13.2\n- CLI Version: 3.13.2\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: ssr, devtools, build, vite, vue, hooks, css, components, runtimeConfig, router, ignore, app, site, robots, routeRules, ogImage, schemaOrg, icon, postcss, nitro, modules, vitalizer, pwa, ui\n- Runtime Modules: @nuxt/ui@2.18.7, @nuxtjs/device@3.2.4, @vueuse/nuxt@11.1.0, @pinia/nuxt@0.5.5, @nuxtjs/seo@2.0.0-rc.18, @vite-pwa/nuxt@0.10.5, nuxt-vitalizer@0.10.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nNot sure how to provide a reproduction since the issue only appears once i build my app.\n\n### Describe the bug\n\nI need to render dynamic templates on the server. For this I have set `vue.runtimeCompiler: true` inside the nuxt config. I also have written a simple `RenderTemplate.vue` component that gets passed a template string and renders the appropriate content.\n\n```ts\n\u003Cscript setup lang=\"ts\">\n // Custom components we allow to render\n import {\n KlzAudio,\n // Tuncated full list...\n } from '#components';\n\n interface Props {\n template: string;\n // eslint-disable-next-line\n options?: any;\n }\n\n const props = withDefaults(defineProps\u003CProps>(), {\n options: {}\n });\n\n const compiledTemplate = computed(() => {\n return defineComponent({\n components: {\n KlzAudio,\n // Tuncated full list...\n },\n props: {\n options: {\n type: Object,\n default: () => ({})\n }\n },\n template: props.template\n });\n });\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003Ccomponent\n :is=\"compiledTemplate\"\n ref=\"compRef\"\n :options=\"props.options\"\n >\u003C/component>\n \u003C/div>\n\u003C/template>\n```\n\nThis works just fine in development mode or when I build using `ssr: false`. In development I have no issues also with `ssr: true` everything works as expected and If I inspect the source code of the pages where I use the `RenderTemplate` component I also see the rendered HTML just fine. But when I build my app using `npx nuxi build --preset=cloudflare_pages` and try to run the server I get:\n\n```\nOn-the-fly template compilation is not supported in the ESM build of @vue/server-renderer. All templates must be pre-compiled into render functions.\n```\n\nUPDATE: This only happens if i use the `cloudflare_pages` preset with `node-server` it works just fine.\n\nI have only found one other issue that mentioned this exact error: https://github.com/nuxt/nuxt/issues/13358\n\nSadly the fix suggested does not work in my scenario since I render more complex components and would get other errors related to not being in the nuxt context using `renderString()`.\n\nI also found that using `render` instead of `template` together with `compile` resolves the \"on-the-fly\" error but when looking at the source of my page the dynamically rendered content is not part of the HTML rendered on the server which is a big issue.\n\nResolves initial error but does not render HTML content on the server:\n```ts\nconst compiledTemplate = computed(() => {\n return defineComponent({\n components: {\n KlzAudio,\n // Truncated full list...\n },\n props: {\n options: {\n type: Object,\n default: () => ({})\n }\n },\n render: compile(props.template)\n });\n});\n```\n\nHow can I fix this issues? Why is it working in dev but not when building the app? \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2964,2967,2970],{"name":2965,"color":2966},"pending triage","E99695",{"name":2968,"color":2969},"needs reproduction","FBCA04",{"name":2971,"color":2972},"closed-by-bot","ededed",29769,"On-the-fly template compilation is not supported in the ESM build of @vue/server-renderer.","2024-11-11T02:00:16Z","https://github.com/nuxt/nuxt/issues/29769",0.67749083,{"description":2979,"labels":2980,"number":2982,"owner":2903,"repository":2923,"state":2924,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Environment\n\n- Node version: 22.9.0 (Docker image 22.9.0-alpine)\n- Nuxt version: 3.14.1592\n- Package manager: pnpm@9.14.2\n- nuxt/ui module version: 2.19.2\n- package.json\n ```\n {\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\"\n },\n \"dependencies\": {\n \"@nuxt/ui\": \"^2.19.2\",\n \"nuxt\": \"^3.14.1592\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"packageManager\": \"pnpm@9.14.2+sha512.6e2baf77d06b9362294152c851c4f278ede37ab1eba3a55fda317a4a17b209f4dbb973fb250a77abc463a341fcb1f17f17cfa24091c4eb319cda0d9b84278387\"\n }\n ```\n- Dockerfile\n ```\n ARG NODE_DOCKER_IMAGE=22.9.0-alpine\n FROM node:$NODE_DOCKER_IMAGE AS base\n \n ARG PORT=3000\n \n ENV NODE_ENV=production\n \n WORKDIR /app\n # Build\n FROM base AS builder\n \n RUN npm install -g pnpm\n \n COPY --link package.json .\n COPY --link pnpm-lock.yaml .\n \n RUN pnpm install --production=true\n \n COPY --link . .\n \n RUN pnpm build\n \n # Run\n FROM base\n \n ENV PORT=$PORT\n \n COPY --from=builder /app/.output /app/.output\n \n COPY --from=builder /app/docker-entrypoint.sh /usr/local/bin/docker-entrypoint\n \n RUN chmod +x /usr/local/bin/docker-entrypoint\n \n ENTRYPOINT [\"docker-entrypoint\"]\n ```\n\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\n1. Create the \"frontend\" Nuxt app `pnpx nuxi@latest init frontend`\n2. `cd frontend`\n3. Add the \"nux/ui\" module `pnpx nuxi@latest module add ui`\n4. Put the Dockerfile described inside the frontend folder\n5. `docker build .`\n\n### Description\n\nThe build fails:\n```\n=> ERROR [builder 6/6] RUN pnpm build 3.4s\n------ \n > [builder 6/6] RUN pnpm build: \n0.512 \n0.512 > nuxt-app@ build /app \n0.512 > nuxt build \n0.512 \n0.658 Nuxt 3.14.1592\n1.374 [nuxt:tailwindcss] ℹ Using default Tailwind CSS file\n1.589 ℹ Nuxt Icon server bundle mode is set to local\n3.009 ℹ Building client...\n3.018 ℹ vite v5.4.11 building for production...\n3.040 ℹ transforming...\n3.350 ℹ ✓ 57 modules transformed.\n3.351 \n3.351 ERROR x Build failed in 331ms\n3.351 \n3.351 \n3.351 ERROR Nuxt Build Error: [vite:css] [postcss] Cannot find module 'tailwindcss/lib/lib/defaultExtractor.js'\n3.351 Require stack:\n3.351 - /app/.nuxt/nuxtui-tailwind.config.cjs\n3.351 file: /app/node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 \n3.351 Require stack:\n3.351 - .nuxt/nuxtui-tailwind.config.cjs\n3.351 file: node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)\n3.351 at Function.resolve (node:internal/modules/helpers:145:19)\n3.351 at _resolve (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:241814)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:244531)\n3.351 at .nuxt/nuxtui-tailwind.config.cjs:2:60\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at .nuxt/tailwind.config.cjs:7:1\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:56:30\n3.351 at loadConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:58:6)\n3.351 at getTailwindConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:71:116)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:100:92\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/processTailwindFeatures.js:46:11\n3.351 at plugins (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/plugin.js:38:69)\n3.351 at LazyResult.runOnRoot (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:329:16)\n3.351 at LazyResult.runAsync (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:258:26)\n3.351 at LazyResult.async (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:160:30)\n3.351 at LazyResult.then (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:404:17)\n3.351 \n3.370 ELIFECYCLE Command failed with exit code 1.\n```\n\n### Additional context\n\nMaybe I'm facing the same problem stated in https://github.com/nuxt/ui/issues/1689\n\n### Logs\n\n```shell-script\n\n```",[2981],{"name":2914,"color":2915},2785,"Nuxt Build Error at build time with Docker","2024-11-27T10:23:20Z","https://github.com/nuxt/ui/issues/2785",0.67951477,{"description":2988,"labels":2989,"number":2992,"owner":2903,"repository":2923,"state":2924,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2990,2991],{"name":2943,"color":2944},{"name":2917,"color":2918},3525,"Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.6801562,{"description":2998,"labels":2999,"number":3002,"owner":2903,"repository":2923,"state":2924,"title":3003,"updated_at":3004,"url":3005,"score":3006},"### 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.",[3000,3001],{"name":2943,"color":2944},{"name":2917,"color":2918},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.68135875,{"description":3008,"labels":3009,"number":3014,"owner":2903,"repository":2923,"state":2924,"title":3015,"updated_at":3016,"url":3017,"score":3018},"### Description\n\n I wanted to ask if you have considered implementing a server-side table feature in Nuxt UI v3, similar to the functionality provided by Vuetify's DataTable component.\n\nVuetify's DataTable offers built-in support for server-side pagination, filtering, and sorting, which makes it an excellent solution for handling large datasets efficiently. It would be fantastic to see a similar feature integrated into Nuxt UI v3. \nI would love to hear your thoughts on this feature and whether it's something that could be considered for future releases.\n\nThank you for your time and attention!",[3010,3013],{"name":3011,"color":3012},"enhancement","a2eeef",{"name":2917,"color":2918},3023,"I would like to ask, have you considered making a server side table in v3?","2025-01-13T10:43:59Z","https://github.com/nuxt/ui/issues/3023",0.6823182,["Reactive",3020],{},["Set"],["ShallowReactive",3023],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fpjgZJLrb1-4E68xXC76Ik7dynejjcPjfYIwtG1FIxrU":-1},"/nuxt/ui/3052"]