\n \u003C/template>\n\u003C/UModal>\n```\n\n\n### Description\n\nselect menu's search input always autofocus inside modal, even when the autofocus is set to false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2867,2870,2873],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"v3","49DCB8",{"name":2874,"color":2875},"triage","ffffff",3933,"nuxt","ui","open","SelectMenu's autofocus doesn't work inside Modal","2025-04-19T06:22:26Z","https://github.com/nuxt/ui/issues/3933",0.6625081,{"description":2885,"labels":2886,"number":2890,"owner":2877,"repository":2878,"state":2879,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Environment\n\n- Ubuntu (WSL 2)\n- Package manager Bun\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n[Reproduction repository](https://github.com/sergiooak/vue-nuxtui-bun-type-import)\n\n\n### Description\n\nI found a weird bug while import types from @nuxt/ui using the syntax \"import { type ComponentProps} from @nuxt/ui\"\nIt took me a long time to pinpoint what was causing the bug. If i use this syntax, and do a fresh install, in my case, bun i && bun dev, I got this weird \"internal\" error from tailwind without point exactly where the error is.\n\nIf I clean the node_modules rewrite the import to \"import type {ComponentProps} from @nuxt/ui\" bun i && bun dev, the problem solves.\n\nI don't know if this is bun related or not, I am creating a minimal reproduction repo using npm and bun ASAP\n(I've just already created the issue in case someone find this bug in the meantime)\n\n### Additional context\n\nThe bug occurs only when using bun install with this specific import syntax for @nuxt/ui. Other imports using the same syntax work as expected. If bun install is run without this syntax, and the code is then adjusted accordingly, everything works fine. I only noticed this issue a few commits later due to this behavior\n\n### Logs\n\n```shell-script\n✘ [ERROR] Could not resolve \"../pkg\"\n\n node_modules/lightningcss/node/index.js:16:27:\n 16 │ module.exports = require(`../pkg`);\n ╵ ~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38:\n 190 │ ...inding = require('@tailwindcss/oxide-linux-x64-gnu')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38:\n 177 │ ...nding = require('@tailwindcss/oxide-linux-x64-musl')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476\n let error = new Error(text);\n ^\n\nError: Build failed with 3 errors:\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\nnode_modules/lightningcss/node/index.js:16:27: ERROR: Could not resolve \"../pkg\"\n at failureErrorWithLog (/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476:15)\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:945:25\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1354:9\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {\n errors: [Getter/Setter],\n warnings: [Getter/Setter]\n}\n```",[2887,2888,2889],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},3039,"Unexpected Bug with Tree-Shaking Type Imports in @nuxt/ui","2025-01-08T08:12:01Z","https://github.com/nuxt/ui/issues/3039",0.6675794,{"description":2896,"labels":2897,"number":2902,"owner":2877,"repository":2878,"state":2879,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Description\n\nHi, I'm having a hard time applying transition to dark / light background.\n\nMy `main.css` file is as follows.\n\nChanging the background color from `slate` to `stone`, for example, works fine.\n\nThe problem is just for the light / dark theme transition.\n\n```\n:root {\n --ui-bg: var(--ui-color-neutral-100);\n}\n\n.dark {\n --ui-bg: var(--ui-color-neutral-900);\n}\n\n@layer base {\n body {\n @apply transition-colors duration-1000;\n }\n}\n```\n\nHere is the function that changes the theme:\n\n```\nconst isDark = computed({\n get() {\n return colorMode.value === 'dark';\n },\n set() {\n colorMode.preference = colorMode.value === 'dark' ? 'light' : 'dark';\n },\n});\n```\n\nAny help would be appreciated, thanks!\n",[2898,2901],{"name":2899,"color":2900},"question","d876e3",{"name":2871,"color":2872},3645,"Applying transition-colors to light / dark theme","2025-03-21T16:20:57Z","https://github.com/nuxt/ui/issues/3645",0.67436886,{"description":2908,"labels":2909,"number":2912,"owner":2877,"repository":2878,"state":2879,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Description\n\nHi there,\n\nI'm really curious about how Nuxt UI is handling trailing slashes. In the Nuxt Content repo I can see they are using `ufo` to remove the trailing slashes, but in the Nuxt UI repo I can't find how you get rid of it. Even tho I know you can do these things on Vercel and Netlify, I'm curious how you handle it in Nuxt UI.\n\nIn my case, route.path is returning a path with a trailing slash and breaks my `queryCollection`...\n\n```vue\nconst { data: page } = await useAsyncData(\n `${route.path}/.navigation`,\n async () => {\n return await queryCollection('content').path(route.path).first();\n }\n);\n```",[2910,2911],{"name":2899,"color":2900},{"name":2871,"color":2872},3285,"Trailing slashes","2025-02-10T13:25:12Z","https://github.com/nuxt/ui/issues/3285",0.6841115,{"description":2918,"labels":2919,"number":2923,"owner":2877,"repository":2878,"state":2879,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Environment\n\nnode22, nuxtui300-b3 and nuxt3\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv.3.0.0-beta3\n\n### Reproduction\n\nYou can reproduce from the components page for modal and drawer. Open the drawer, the bottom drawer appears, and rest of page shifts from removal of scrollbar. Same does not occur on the modal component.\n\n### Description\n\nThe modal component properly handles overflow and prevents shifting of the main page layout when open. The drawer component does not. Would like to see the drawer prevent layout shift from the scroll bar removal, like is done on the modals. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2920,2921,2922],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},3523,"Drawer shifts layout unlike modal","2025-03-23T17:40:06Z","https://github.com/nuxt/ui/issues/3523",0.6905614,{"description":2929,"labels":2930,"number":2934,"owner":2877,"repository":2935,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"- [x] `/modules`\n- [x] `/community/repositories`\n- [x] `/community/partners`\n- [x] `/resources/showcases`",[2931],{"name":2932,"color":2933},"enhancement","1ad6ff",597,"nuxt.com","closed","[Responsive] Display aside filters on list pages","2023-02-15T12:32:35Z","https://github.com/nuxt/nuxt.com/issues/597",0.6162009,{"description":2942,"labels":2943,"number":2945,"owner":2877,"repository":2878,"state":2936,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### 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.",[2944],{"name":2899,"color":2900},2244,"UTable Expandable questions?","2024-11-05T14:52:12Z","https://github.com/nuxt/ui/issues/2244",0.6203729,{"description":2951,"labels":2952,"number":2955,"owner":2877,"repository":2878,"state":2936,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: compatibilityDate, devtools, future, experimental, modules, vite, css, typescript\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/test-utils@3.17.2, @nuxt/icon@1.11.0, @nuxt/ui@3.0.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu\n\n### Description\n\nThe InputMenu component only shows filtered items when opening it with a selected item. This is confusing, and differs from expected behavior. In its current state, the InputMenu would only be usable, if the user deletes the text in the field, which is not clear nor expected.\n\nExpected behavior: If one opens the select menu by clicking on the button, it shows all available values, with the currently selected value highlighted. Only when changing the text of the input field, it filters for the value entered.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2953,2954],{"name":2868,"color":2869},{"name":2871,"color":2872},3620,"InputMenu shows only selected item when opening","2025-03-27T15:27:51Z","https://github.com/nuxt/ui/issues/3620",0.63393426,{"description":2961,"labels":2962,"number":2964,"owner":2877,"repository":2878,"state":2936,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.0\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.2\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.5.7, @nuxt/fonts@0.7.2, @nuxt/ui@2.19.0, @vueuse/nuxt@10.11.1, @pinia/nuxt@0.5.5, @pinia-plugin-persistedstate/nuxt@1.2.1, @nuxtjs/i18n@8.5.6, @nuxtjs/tailwindcss@6.12.2, @vite-pwa/nuxt@0.10.6\n- Build Modules: -\n------------------------------\n\n### Version\n\nv.2.19.0\n\n### Reproduction\n\nUpgrade nuxt/ui to latest 2.19.0 version\n\n### Description\n\nSelectMenu component is broken from what it seems to be a mistake in the a merge conflict.\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2963],{"name":2868,"color":2869},2534,"Critical bug in SelectMenu.vue","2024-11-05T16:58:09Z","https://github.com/nuxt/ui/issues/2534",0.645886,{"description":2970,"labels":2971,"number":2974,"owner":2877,"repository":2878,"state":2936,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2972,2973],{"name":2899,"color":2900},{"name":2871,"color":2872},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.6531999,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fq2f0Ref1sK4VSmFT3M3hencOp2ym3HviRcqfJ-0Qfqw":-1},"/nuxt/ui/3595"]