\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst flip = ref(false);\r\n\u003C/script>\r\n```\r\n\r\nWhile this works fine with nuxt-icon during development, it breaks in a Prod build. The transformations no longer get applied.\r\n\r\nIt would be great if nuxt-icon could also support these props, if possible. I'm open to help with this issue if someone could give me some pointers where to start.",[],138,"icon","[Feature Request] Support Iconify Transformations","2024-03-15T09:15:14Z","https://github.com/nuxt/icon/issues/138",0.7485545,{"description":3164,"labels":3165,"number":3175,"owner":3147,"repository":3147,"state":3149,"title":3176,"updated_at":3177,"url":3178,"score":3179},"### Describe the feature\r\n\r\nEspecially when it comes to handling URL state, I've seen the wildest implementations.\r\nIt would be great to have two simple helper composables which create \"reactive\" router params and router query values.\r\nThat way, it would be even easier to sync URL state (and we could properly document + advise it).\r\n\r\nThis [already exists in VueUse](https://vueuse.org/router/useRouteParams/) but does not utilize `navigateTo`.\r\n\r\nExample syntax (adapted from VueUse example)\r\n\r\n```ts\r\nconst search = useRouteQuery('search')\r\n\r\nconst otherSearch = useRouteQuery('search', 'foo') // default value\r\n\r\nconst page = useRouteQuery('page', '1', { transform: Number }) // with transform function too\r\n\r\nconsole.log(search.value) // same as route.query.search\r\nsearch.value = 'foobar' // Calls navigateTo({ query: { search: 'foobar' } }, { replace: true })\r\n```\r\n\r\n---\r\n\r\nRelated issue (was more bare-bone): https://github.com/nuxt/nuxt/issues/24365\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [X] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3166,3169,3172],{"name":3167,"color":3168},"enhancement","8DEF37",{"name":3170,"color":3171},"workaround available","11376d",{"name":3173,"color":3174},"needs details","493824",24788,"`useRouteParams` and `useRouteQuery` for Nuxt","2024-09-13T10:57:55Z","https://github.com/nuxt/nuxt/issues/24788",0.75125694,{"description":3181,"labels":3182,"number":3185,"owner":3147,"repository":3148,"state":3186,"title":3187,"updated_at":3188,"url":3189,"score":3190},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.2.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.4\n- Package Manager: bun@1.2.17\n- Builder: -\n- User Config: css, modules, nitro, i18n, imports, runtimeConfig, icon, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@10.0.6, @nuxt/ui-pro@3.3.1, @nuxt/eslint@1.9.0, @nuxtjs/html-validator@2.1.0, @nuxt/image@1.11.0, @vueuse/nuxt@13.7.0, @artmizu/nuxt-prometheus@2.5.2, @nuxtjs/seo@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.1\n\n### Reproduction\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(\"\");\nconst items: Array\u003Cstring | number> = [1, \"2\", 3];\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUForm :state=\"value\" class=\"flex max-w-72 flex-col space-y-4 py-8\">\n \u003CUFormField label=\"UInputMenu\">\n \u003CUInputMenu v-model=\"value\" :items placeholder=\"UInputMenu\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelect\">\n \u003CUSelect v-model=\"value\" :items placeholder=\"USelect\" />\n \u003C/UFormField>\n \u003CUFormField label=\"USelectMenu\">\n \u003CUSelectMenu v-model=\"value\" :items placeholder=\"USelectMenu\" />\n \u003C/UFormField>\n \u003C/UForm>\n\u003C/template>\n```\n\n### Description\n\nAfter updating to version 3.3.1, the InputMenu, Select and SelectMenu component's placeholder value is not shown, if the value is not found in the items array. In version 3.3.0 the placeholder correctly shows up.\n\nNuxt UI 3.3.0\n\u003Cimg width=\"350\" height=\"300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b0937d4-7640-4277-8169-ff192bc01d97\" />\n\nNuxt UI 3.3.1\n\u003Cimg width=\"410\" height=\"285\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3d744e11-748b-4b3c-a236-fcee8fdcd765\" />\n\n\u003Cimg width=\"395\" height=\"298\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ac7be307-ca5c-4957-a2fb-5721eebdea07\" />\n\nIf the v-model is `undefined` it works just like in 3.3.0, however in my projects I feel like that's not always achievable because of type definitions.\nI know I could set the default value to one of the items' values, but what if I don't want to populate the component by default and just show the placeholder? \nFor this to work in version 3.3.1 I'd have to loosen up the type definitions, so that required fields are not required anymore, which is wrong and I don't feel like I should have to do to keep the behavior of a UI component. \n\nShouldn't we have an exception for falsy values that are sometimes used as default values (empty string, 0...), so the placeholder can be shown without having to explicitly have `undefined` as the default value?\n\n### Additional context\n\nI haven't dug that deep, but I think #4689 introduced this behavior to these components. \n\n### Logs\n\n```shell-script\n\n```",[3183,3184],{"name":3138,"color":3139},{"name":3141,"color":3142},4812,"closed","[InputMenu,Select,SelectMenu] Placeholder not showing in v3.3.1, if item is not found and default value is not undefined or null","2025-08-27T14:42:51Z","https://github.com/nuxt/ui/issues/4812",0.71542376,{"description":3192,"labels":3193,"number":3197,"owner":3147,"repository":3148,"state":3186,"title":3198,"updated_at":3199,"url":3200,"score":3201},"### Description\n\nThis would be a new prop for `UInputTags` that would allow you to set a max length on the items being added. \n\n```\n\u003CInputTags v-model=\"items\" :max-item-length=\"25\" />\n\nconst items = ref([\n \"ok\",\n \"this one would not be ok because of how long it is\"\n])\n```\n\nThough, you could use something like Zod to do form validation, I think this could just apply a `maxlength` to the input itself to prevent typing more than the limit.\n\n### Additional context\n\n_No response_",[3194,3196],{"name":3167,"color":3195},"a2eeef",{"name":3141,"color":3142},4405,"InputTags max item length","2025-07-01T08:35:33Z","https://github.com/nuxt/ui/issues/4405",0.7221349,{"description":3203,"labels":3204,"number":3208,"owner":3147,"repository":3148,"state":3186,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Environment\n\nN/A\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/compassionate-jasper-w2k3lm\n\n### Description\n\nThe `InputMenu` component throws an error if one of the fields provided in `filterFields` resolved to a nullish or non-string value. You can reproduce this in the sandbox by typing in the input box and observing the console.\n\nSo having the following setup errors out, which is a real-world use case I'm encountering this:\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst items = [\n {\n label: 'foo',\n alias: 'something'\n },\n {\n label: 'bar'\n }\n]\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUInputMenu :items :filter-fields=\"['label', 'alias']\" />\n\u003C/template>\n```\n\nThis is caused by `useFilter.contains` being called with a non-string value.\n\nIt is somewhat related to https://github.com/nuxt/ui/issues/3606 which has been addressed previously, but only for primitive item types.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3205,3206,3207],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4509,"InputMenu: error if field field is nullish or non-string","2025-07-12T10:15:32Z","https://github.com/nuxt/ui/issues/4509",0.72598886,{"description":3214,"labels":3215,"number":3221,"owner":3147,"repository":3148,"state":3186,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3216,3217,3218],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3219,"color":3220},"reka-ui","56d799",3993,"InputMenu Clear Search on Select at first click","2025-07-16T10:57:06Z","https://github.com/nuxt/ui/issues/3993",0.7266566,{"description":3227,"labels":3228,"number":3232,"owner":3147,"repository":3148,"state":3186,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Version\n\nLatest commit https://pkg.pr.new/@nuxt/ui@62ab016\n\n### Description\n\nWhen fetching items using [ignore-filter prop ](https://ui.nuxt.com/components/select-menu#with-ignore-filter) `\u003CUSelectMenu>` does not remember the current selection.\n\nCurrently it works only if the selected item stays in the items array which is barely the case if dealing with more than 10 items:\n\nhttps://github.com/user-attachments/assets/f5c6b264-52a5-4d8b-b015-242e36d91fdb\n\nThis happens in two cases:\n\n1. When selecting an item the searchTerm gets resetted, the items-array changes and the selected item is no more in it -> Select menu label becomes empty\n2. When an item is selected, but searching for other items that dont include seleced item -> Select menu label becomes empty\n\n### Reproduction\n\nAlso reproducable in the docs:\nhttps://ui.nuxt.com/components/select-menu#with-ignore-filter\n\nhttps://github.com/user-attachments/assets/ec3065bb-7cc2-4976-9dde-da99dd2311b6\n\nHere case 1 never happens because the jsonplaceholder-api only has just 5 user-items so the selected user is always in the default empty search result. BUT case 2 happens: Select a user, open select again, type in any other name that doesnt include first user -> Select menu label becomes empty (weirdly tho, the avatar stays)",[3229,3230,3231],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4582,"SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4582",0.72669005,{"description":3238,"labels":3239,"number":3249,"owner":3147,"repository":3148,"state":3186,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Description\n\nI want to use the `InputMenu` component with multiple selections and a list of data retrieved from an API.\nHowever, when I select an item through a search, it is not displayed correctly because its data is not necessarily present in the list of available options returned by the API.\n\nA reproduction of my situation is available on this [CodeSandbox](https://codesandbox.io/p/devbox/upbeat-snyder-m27rfr) in the `index.vue` page.\nFor an example, search for the first name “Emma” and select the two suggested items. The first one is found in the initial range of data available from the API, while the other is located in a more distant range.\n\nDo you have any ideas on possible solutions to resolve this issue? Could it perhaps be a bug in the component?",[3240,3243,3244,3247],{"name":3241,"color":3242},"question","d876e3",{"name":3141,"color":3142},{"name":3245,"color":3246},"closed-by-bot","ededed",{"name":3248,"color":3246},"stale",3348,"InputMenu multiple with async data","2025-06-18T09:02:06Z","https://github.com/nuxt/ui/issues/3348",0.7296155,{"description":3255,"labels":3256,"number":3260,"owner":3147,"repository":3148,"state":3186,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.2.0\n- Nuxt Version: 3.17.7\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: bun@1.2.17\n- Builder: -\n- User Config: future, experimental, css, modules, nitro, i18n, imports, runtimeConfig, icon, compatibilityDate\n- Runtime Modules: @nuxtjs/i18n@9.5.6, @nuxt/ui-pro@3.2.0, @nuxt/eslint@1.5.2, @nuxtjs/html-validator@2.1.0, @nuxt/image@1.10.0, @vueuse/nuxt@13.5.0, @artmizu/nuxt-prometheus@2.5.0, @nuxtjs/seo@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nThe issue is really straight-forward, example code: \n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(\"\");\nconst items = [\"Item 1\", \"Item 2\", \"Item 3\"];\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"space-y-4\">\n \u003CUFormField label=\"USelectMenu\">\n \u003CUSelectMenu v-model=\"value\" placeholder=\"Placeholder\" :items />\n \u003C/UFormField>\n \u003CUFormField label=\"USelect\">\n \u003CUSelect v-model=\"value\" placeholder=\"Placeholder\" :items />\n \u003C/UFormField>\n \u003C/div>\n\u003C/template>\n\n```\n\n### Description\n\nIf the model-value is an empty string, the USelectMenu placeholder doesn't show. This behavior is different than the USelect component, where the placeholder is shown without having to use `undefined` as the v-model's value. \n\n### Additional context\n\nI know I could use `undefined` for the value here, however in my real code the v-model is bound to a non-optional value, so if I were to initialize it as `undefined`, TypeScript would freak out. Also, because these components are really similar, these behaviors shouldn't differ in my opinion. \n\n\u003Cimg width=\"200\" height=\"143\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/49a5d11d-2212-41d7-81b3-202692a20a8a\" />\n\n### Logs\n\n```shell-script\n\n```",[3257,3258,3259],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4528,"[SelectMenu]: Placeholder value not shown if v-model is an empty string","2025-07-16T10:43:41Z","https://github.com/nuxt/ui/issues/4528",0.7307451,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmMzYZNwzhGhhjTK30VlTxyIkaeezm_LckhI91wNrrmo":-1},"/nuxt/ui/4829"]