`\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst items = ref([ 'foo', 'bar' ])\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUInputMenu :items=\"items\" multiple @change=\"console.log('change')\" />\n\u003C/template>\n```\n\n### Description\n\nChange event on UInputMenu is not triggered by clicking on the delete-icon.\n\nSeems like deleting by clicking the item in the list like mentioned here https://github.com/nuxt/ui/issues/3756 is fixed but clicking the delete-icon still wont triggers the @change event\n\n### Additional context\n\nwhile trying to recreate the issue in codesandbox i also got this error\n\n### Logs\n\n```shell-script\nUncaught TypeError: Cannot read properties of undefined (reading 'filter')\n at onRemoveTag (/_nuxt/@fs/project/workspace/node_modules/.pnpm/@nuxt+ui@3.0.2_embla-carousel@8.5.2_typescript@5.8.2_vite@6.2.4/node_modules/@nuxt/ui/dist/runtime/components/InputMenu.vue:182:42)\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:204:17)\n at emit (runtime-core.esm-bundler.js?v=d5312b36:6406:5)\n at runtime-core.esm-bundler.js?v=d5312b36:8115:45\n at Object.handleRemoveTag [as onRemoveValue] (/_nuxt/@fs/project/workspace/node_modules/.pnpm/reka-ui@2.1.1_typescript@5.8.2_vue@3.5.13/node_modules/reka-ui/dist/TagsInput/TagsInputRoot.js?v=d5312b36:56:9)\n at handleDelete (/_nuxt/@fs/project/workspace/node_modules/.pnpm/reka-ui@2.1.1_typescript@5.8.2_vue@3.5.13/node_modules/reka-ui/dist/TagsInput/TagsInputItemDelete.js?v=d5312b36:24:15)\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:204:17)\n at HTMLButtonElement.invoker (runtime-dom.esm-bundler.js?v=d5312b36:720:5)\n```",[2921,2924,2927],{"name":2922,"color":2923},"bug","d73a4a",{"name":2925,"color":2926},"duplicate","cfd3d7",{"name":2908,"color":2909},3890,"closed","UInputMenu change event is not triggered by clicking delete-icon (when multiple=true)","2025-04-14T13:56:50Z","https://github.com/nuxt/ui/issues/3890",0.74352527,{"description":2935,"labels":2936,"number":2939,"owner":2911,"repository":2912,"state":2929,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Description\n\nI am new using Nuxt UI, and I am loving it.\nI personally believe buttons look better when they are wider than taller, therefore I like to add more padding in the x axis, but I don't want to do this for each button.\n\nI am currently doing it like this:\n\n```html\n\u003CUButton\n to=\"/login\"\n size=\"xl\"\n color=\"warning\"\n variant=\"solid\"\n class=\"font-semibold px-4\"\n >\n Iniciar sesión\n \u003C/UButton>\n```\n\nbut I don't know how to add the option for all buttons.\nI tried doing this in the app.config.ts:\n\n```js\nui: {\n button: {\n slots: {\n base: 'px-4 cursor-pointer'\n },\n}\n \n```\n\nand the cursor-pointer worked, but the px-4 didn't work. Any idea on how to make this work?",[2937,2938],{"name":2905,"color":2906},{"name":2908,"color":2909},3646,"How do I change the padding of all buttons globally?","2025-03-24T01:29:59Z","https://github.com/nuxt/ui/issues/3646",0.7474378,{"description":2945,"labels":2946,"number":2951,"owner":2911,"repository":2912,"state":2929,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Description\n\nI would like to propose the addition of Khmer language support (ភាសាខ្មែរ), which is the national language of Cambodia 🇰🇭. Adding Khmer will enhance accessibility for Khmer-speaking users and improve their experience when using the Nuxt/UI framework.\n\u003Ch1>Motivation\u003C/h1>\nCurrently, the absence of Khmer language support limits usability for a significant number of users who prefer to interact with applications in their native language. By including Khmer, we can:\n1. Broaden our user base in Cambodia and among Khmer-speaking communities worldwide.\n2. Improve user experience and engagement for Khmer-speaking developers and end-users.\n3. Align with our goal of inclusivity and accessibility in software development.\n\u003Ch1>Proposed Implementation\u003C/h1>\n1. Language Files: Create and include translation files for Khmer.\n2. Testing: Ensure that all components are correctly translated and function as expected in Khmer.\n3. Documentation: Update the documentation to reflect the new language support, including usage examples.\n\u003Ch1>Additional Notes\u003C/h1>\nThis is my first time to open a PR in Nuxt UI repo so if there are any specific guidelines or requirements for adding new languages, please let me know, and I would be happy to follow them.\nThank you for considering this request!\n\n### Additional context\n\n_No response_",[2947,2950],{"name":2948,"color":2949},"enhancement","a2eeef",{"name":2908,"color":2909},3118,"Request to Add Khmer Language Support","2025-01-25T13:14:14Z","https://github.com/nuxt/ui/issues/3118",0.7573779,{"description":2957,"labels":2958,"number":2964,"owner":2911,"repository":2912,"state":2929,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[2959,2960,2961],{"name":2948,"color":2949},{"name":2908,"color":2909},{"name":2962,"color":2963},"triage","ffffff",3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.7660117,{"description":2970,"labels":2971,"number":2974,"owner":2911,"repository":2912,"state":2929,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.16.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `pnpm@10.6.3`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `vite`, `colorMode`, `nitro`, `future`, `compatibilityDate`, `hub`, `app`, `schemaOrg`, `i18n`\n- Runtime Modules: `@nuxthub/core@0.8.18`, `@nuxt/ui@3.0.0`, `@nuxtjs/i18n@9.3.2`, `@nuxtjs/seo@3.0.1`, `nuxt-auth-utils@0.5.17`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dry-sun-8ddkqr\n\n### Description\n\nThe events of the `USelectMenu` do not work as intended. As you can see in the reproduction, the `change` event of the `UForm` is expected to be emitted every time you select/deselect/create an item, but instead it's emitted only a few seemingly random times.\n\nSwitching to the `input` event on the form has the same random behavior.\n\nI am also surprised programmatically changing the list of values doesn't trigger the `update` event on the `USelectMenu`, but that could be by design and is not really the blocking issue here.\n\nMy reproduction code is a simplification of my real code. It is very similar to the documentation example for creating items, main difference is the multi selection. However the issue also occurs without multi selection.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2972,2973],{"name":2922,"color":2923},{"name":2908,"color":2909},3660,"`USelectMenu` doesn't emit `UForm`.`change` as expected","2025-04-04T16:14:05Z","https://github.com/nuxt/ui/issues/3660",0.7730397,{"description":2980,"labels":2981,"number":2984,"owner":2911,"repository":2912,"state":2929,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nMy current nuxt.config.ts file looks like this:\n\n```js\nexport default defineNuxtConfig({\n compatibilityDate: \"2024-04-03\",\n ssr: false,\n future: {\n compatibilityVersion: 4,\n },\n modules: [\"@nuxt/ui\"],\n hooks: {\n \"prerender:routes\"({ routes }) {\n routes.clear();\n },\n },\n routeRules: {\n \"/\": {\n redirect: \"dashboard\",\n },\n },\n ui: {\n colorMode: false,\n },\n devtools: { enabled: true },\n});\n```\n\nThe project it's pretty empty.\n\n### Description\n\nI'm receiving this error message:\n\n\n\n### Additional context\n\nMy app.vue file:\n\n```vue\n\u003Ctemplate>\n \u003CUApp>\n \u003CNuxtLayout>\n \u003CNuxtPage />\n \u003C/NuxtLayout>\n \u003C/UApp>\n\u003C/template>\n\n\u003Cstyle>\n@import \"tailwindcss\";\n@import \"@nuxt/ui\";\n\n@theme {\n --font-sans: \"Poppins\", sans-serif;\n}\n\u003C/style>\n```\n\n### Logs\n\n```shell-script\nERROR Pre-transform error: [unimport] failed to find \"useColorMode\" imported from \"#imports\"\n✔ Nuxt Nitro server built in 1026 ms\nℹ Vite client warmed up in 2ms\nERROR Internal server error: [unimport] failed to find \"useColorMode\" imported from \"#imports\"\n Plugin: nuxt:imports-transform\n File: /home/app/node_modules/@nuxt/ui/dist/devtools/runtime/DevtoolsRenderer.vue?macro=true\n at file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:120:17\n at Array.forEach (\u003Canonymous>)\n at file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:117:44\n at Array.forEach (\u003Canonymous>)\n at parseVirtualImportsRegex (file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:115:122)\n at detectImportsRegex (file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:96:28)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async injectImports (file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:1387:61)\n at async Object.injectImportsWithContext [as injectImports] (file:///home/app/node_modules/unimport/dist/shared/unimport.54fdbc5b.mjs:1259:20)\n at async TransformPluginContext.transform (file:///home/app/node_modules/nuxt/dist/index.mjs:2633:30)\n at async file:///home/app/node_modules/vite-plugin-inspect/dist/index.mjs:1120:17\n at async PluginContainer.transform (file:///home/app/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:49096:18)\n at async loadAndTransform (file:///home/app/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:51929:27)\n at async viteTransformMiddleware (file:///home/app/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:61881:24)\n```",[2982,2983],{"name":2922,"color":2923},{"name":2908,"color":2909},2788,"Setting colorMode to false triggers an error","2024-11-28T09:51:56Z","https://github.com/nuxt/ui/issues/2788",0.7748383,{"description":2990,"labels":2991,"number":2998,"owner":2911,"repository":2911,"state":2929,"title":2999,"updated_at":3000,"url":3001,"score":3002},"For now, the [modules testing](https://v3.nuxtjs.org/getting-started/testing/#testing-modules) chapter is in the \"Getting Started\" section. We should move this section to the Modules Author guide",[2992,2995],{"name":2993,"color":2994},"documentation","5319e7",{"name":2996,"color":2997},"3.x","29bc7f",14962,"[Docs] Move modules testing section","2023-04-20T13:10:13Z","https://github.com/nuxt/nuxt/issues/14962",0.77785265,{"description":3004,"labels":3005,"number":3008,"owner":2911,"repository":2912,"state":2929,"title":3009,"updated_at":3010,"url":3011,"score":3012},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3006,3007],{"name":2922,"color":2923},{"name":2908,"color":2909},3220,"Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3220",0.7796767,{"description":3014,"labels":3015,"number":3019,"owner":2911,"repository":2912,"state":2929,"title":3020,"updated_at":3021,"url":3022,"score":3023},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: yarn@4.5.0\n- Builder: -\n- User Config: app, site, modules, ui, imports, nitro, i18n, devtools, runtimeConfig, experimental, future, content\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.11, @nuxtjs/seo@2.1.0, @nuxt/content@3.0.0, @nuxtjs/i18n@9.1.2, @nuxt/scripts@0.9.5, @nuxt/fonts@0.10.3\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.11\n\n### Reproduction\n\nThe reproduction uses the documentation's Toast usage example from https://ui3.nuxt.dev/components/toast (the `showToast` function) adjusted to the needs of my project (version tracker):\n\n```ts\nconst {data, error} = await useAsyncData('versions', async () => {\n\tthrow createError({statusCode: '404'}) // this is done to simulate an error to trigger the toast\n\treturn {data1: [], data2: []}\n})\n\nconst toast = useToast()\nfunction showToast(what: string, prop?: string) {\n\ttoast.add({\n\t\ttitle: 'Failed to fetch '+what + ' version information.',\n\t\tdescription: versionData[prop]?.[0]?.version ? 'Showing potentially stale data until next status update' : 'Retrying status fetch in 30 seconds.',\n\t\ticon: 'i-lucide-x',\n\t\tcolor: 'error',\n\t\tduration: 10000\n\t})\n}\nonNuxtReady(()=>{\n\tif (error.value) {\n\t\tshowToast('Data1', 'data1')\n\t\tshowToast('Data2', 'data2')\n\t}\n})\n```\n\n### Description\n\nWhen 2 toasts are added close to one another (in the execution time), sometimes they don't both get rendered, even though the `add` is called. The chance of one of them not getting rendered increases the closer they are.\n\nFor example, in the reproduction, the second toast almost never gets rendered. \n\nMeanwhile, having the toast function in a catch clause (with a `createError` in the try clause) has higher chances of rendering both toasts, but still inconsistently.\n\n### Additional context\n\nThis image shows only the first toast gets rendered (the white border indicates end of page):\n\n\n\n### Logs\n\n```shell-script\n\n```",[3016,3017,3018],{"name":2922,"color":2923},{"name":2925,"color":2926},{"name":2908,"color":2909},3166,"Multiple toast creations do not consistently render equivalent number of toasts","2025-01-23T20:11:47Z","https://github.com/nuxt/ui/issues/3166",0.7802795,["Reactive",3025],{},["Set"],["ShallowReactive",3028],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fpb1jCqYdJs-9waES23aod5X9H8Ux1SoKOeJ1W9EPypg":-1},"/nuxt/ui/3876"]