\n\n- [ ] **`UInputEditor`**\nSince Reka UI lacks a native editor component, I recommend integrating a third-party solution like [Quill](https://quilljs.com) or [TipTap](https://tiptap.dev) (which already offers Nuxt/Vue support). Although previously dismissed by the author, this feature remains highly requested by the community. \u003Cbr>\u003Cimg width=\"1009\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4862e9e8-4769-4bd3-a40e-bc89cea5d1a1\" />\n_Related: #2698, #1889, #791_\n\n- [ ] **`UInputTime`**\nImplement the `TimeField` component from Reka UI, this component could support single and range-based time selection.\n_Related: #3089, #3969, #4634_ \u003Cbr>\u003Cimg width=\"175\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7e338f95-eae3-4ef8-81cc-b3db28553b4e\" />\n\n- [ ] **`UInputDate`**\nImplementation of Reka UI’s `DatePicker` and `DateRangePicker`. \u003Cbr>\u003Cimg width=\"608\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fcae5c2d-50ed-4b8b-ac89-b3272626fd48\" />\n_Related: #2524, #2873_\n\n- [ ] **`UInputDateTime`**\nA hybrid component combining `UInputDate` and `UInputTime` for scenarios requiring both date and time inputs. \u003Cbr>\u003Cimg width=\"303\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2372467f-ca86-44a0-9667-6dc3ffa43247\" />\n\n- [ ] **`UInputMonth`**\nIdeal for cases where users need to select a combination of month and year. \u003Cbr>\u003Cimg width=\"249\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7ee72087-0d58-47ca-b0f7-b5c239148d91\" />\n\n- [ ] **`UInputYear`**\nA simpler component for year-only selection. \u003Cbr>\u003Cimg width=\"247\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a841c974-43b7-42a1-ac3c-7fb42e85fafc\" />\n\n- [ ] **`UInputMask`**\nMasked inputs are indispensable for formatting fields like postal codes or national IDs. I suggest leveraging [Vue The Mask](https://github.com/vuejs-tips/vue-the-mask) for implementation. \u003Cbr>\u003Cimg width=\"316\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b2a3150f-a29e-40ad-96c1-32a63b3bd9ac\" />\n_Related: #1303, #510_\n\n- [ ] **`UInputPhone`**\nA phone input with internationalization support, much like `LocaleSelect` (which already displays flags and country names). The [libphonenumber-js](https://www.npmjs.com/package/libphonenumber-js) library could serve as the foundation. \u003Cbr>\u003Cimg width=\"312\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/893a1bf3-130c-49da-b41e-8ebf468569a4\" />\n_Related: #2815_\n\n## Updates to Existing Components\n\n- [ ] **`UPinInput → UInputPin`**\nRename the existing `UPinInput` component to align with the naming convention used across other input components.\n\n- [ ] **`UInput / UTextarea`**\nAdd a native character counter via a `counter` property, configurable using the `min` and/or `max` attributes. Currently, there is an [example](https://ui3.nuxt.dev/components/input#with-character-limit) for this functionality, but a native implementation would improve the developer experience.\n\n### Additional context\n\n_No response_",[3037,3040],{"name":3038,"color":3039},"feature","A27AF6",{"name":3024,"color":3025},3094,"[RFP] The Inputs Update","2025-07-31T02:45:34Z","https://github.com/nuxt/ui/issues/3094",0.7871111,{"description":3047,"labels":3048,"number":3058,"owner":3027,"repository":3027,"state":3029,"title":3059,"updated_at":3060,"url":3061,"score":3062},"Nuxt has a lot of modules to choose from and already supporting bunch of different environments to be hosted on, but very often you could face issues with a module compatibility in various environments which leads to long hours of debugging or questioning all over the place to find out what's actually happening with Nuxt where Nuxt itself has nothing todo with the problem.\n\nWould be nice to have some sort of visual compatibility flags on module page which could display in what kind of environments module can be used.\nfor example:\n\nCompatible with:\ncloudflare wokers\nfirebase\nnetlify\nvercel\netc...\n",[3049,3052,3055],{"name":3050,"color":3051},"enhancement","8DEF37",{"name":3053,"color":3054},"discussion","538de2",{"name":3056,"color":3057},"🍰 p2-nice-to-have","0E8A16",29905,"Modules compatibility information","2024-11-14T10:23:55Z","https://github.com/nuxt/nuxt/issues/29905",0.7929884,{"description":3064,"labels":3065,"number":3067,"owner":3027,"repository":3028,"state":3068,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\n### Description\nHi there,\n\nIn many of the projects I’m working on, I need to display a limited number of items in the command palette when no search is performed and show more items when a search is initiated.\n\nCurrent Issue\nThe `resultLimit` currently controls how many search results are shown, but I want to decouple the initial number of displayed items from the search result limit. Specifically, I want to:\n\n- Display 5 items by default when no search is performed.\n- Increase the number of displayed items to 20 when a search is initiated, controlled by the `resultLimit`, without affecting the initial state.\n- When attempting to conditionally control this behavior using a computed property, the feature does not work as expected.\n\n Versions\n\n@nuxt/ui: ^2.18.2\nnuxt: ^3.12.4\n\nExample\n\n```Javascript\n\u003Ctemplate>\n \u003CUCommandPalette\n command-attribute=\"title\"\n :fuse=\"{\n resultLimit: computedResultLimit\n }\"\n />\n\u003C/template>\n\n\u003Cscript setup>\nconst searchTerm = ref('');\n\nconst computedResultLimit = computed(() => {\n if (!searchTerm.value) {\n return 5;\n }\n return 20;\n});\n\u003C/script>\n```\n",[3066],{"name":3021,"color":3022},2393,"closed","Command Palette: Specific Item Display with Conditional resultLimit Behavior","2024-10-16T09:31:26Z","https://github.com/nuxt/ui/issues/2393",0.7201939,{"description":3074,"labels":3075,"number":3079,"owner":3027,"repository":3028,"state":3068,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nRight now, using the CLI does not create a template for documentation.\n\n### Additional context\n\n_No response_",[3076,3078],{"name":3050,"color":3077},"a2eeef",{"name":3024,"color":3025},2615,"Add a template for documentation in the CLI","2024-11-12T14:57:04Z","https://github.com/nuxt/ui/issues/2615",0.74842507,{"description":3085,"labels":3086,"number":3097,"owner":3027,"repository":3028,"state":3068,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.19.0\n- Nuxt Version: -\n- CLI Version: 3.23.1\n- Nitro Version: -\n- Package Manager: pnpm@10.7.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nfreshly pulled official starter template using\n```bash\nnpx giget@latest gh:nuxt-ui-pro/starter-vue . --force\n```\ncleaned components.d.ts / deleted it\nit has been recreated: but missing ALL nuxtui components:\n\n```js\n/* eslint-disable */\n// @ts-nocheck\n// Generated by unplugin-vue-components\n// Read more: https://github.com/vuejs/core/pull/3399\n// biome-ignore lint: disable\nexport {}\n\n/* prettier-ignore */\ndeclare module 'vue' {\n export interface GlobalComponents {\n LogoPro: typeof import('./src/components/LogoPro.vue')['default']\n RouterLink: typeof import('vue-router')['RouterLink']\n RouterView: typeof import('vue-router')['RouterView']\n }\n}\n```\n\n### Description\n\nThe components.d.ts file generated by `unplugin-vue-components` is incomplete.\n\n### Additional context\n\n```js\nimport { defineConfig } from 'vite'\nimport vue from '@vitejs/plugin-vue'\nimport uiPro from '@nuxt/ui-pro/vite'\n\n// https://vitejs.dev/config/\nexport default defineConfig({\n plugins: [\n vue(),\n uiPro({\n ui: {\n colors: {\n primary: 'green',\n neutral: 'slate'\n }\n },\n prefix: 'U'\n })\n ]\n})\n```\n\n### Logs\n\n```shell-script\n\n```",[3087,3090,3093,3094],{"name":3088,"color":3089},"bug","d73a4a",{"name":3091,"color":3092},"needs reproduction","CB47CF",{"name":3024,"color":3025},{"name":3095,"color":3096},"triage","ffffff",3753,"unplugin components.d.ts not working","2025-03-31T13:04:11Z","https://github.com/nuxt/ui/issues/3753",0.765622,{"description":3103,"labels":3104,"number":3107,"owner":3027,"repository":3028,"state":3068,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Version\n\n3.0.0-alpha.7\n\n### Reproduction\n\n-\n\n### Description\n\nCurrently the type hints for the `modelValue` prop and `update:modelValue` event of the `Select`/`SelectMenu`/`InputMenu` components are incorrect, e.g.:\n\nHere the correct type should be `number`, not the item object:\n\n\nSimilarly, when the `multiple` prop is set, the correct type should be `number[]`, not the item object:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3105,3106],{"name":3088,"color":3089},{"name":3024,"color":3025},2470,"[v3]: wrong types on select inputs components","2024-11-05T16:03:04Z","https://github.com/nuxt/ui/issues/2470",0.7715953,{"labels":3113,"number":3118,"owner":3027,"repository":3027,"state":3068,"title":3119,"updated_at":3120,"url":3121,"score":3122},[3114,3115],{"name":3050,"color":3051},{"name":3116,"color":3117},"3.x","29bc7f",13848,"add noscript support","2025-02-13T09:02:12Z","https://github.com/nuxt/nuxt/issues/13848",0.77288026,{"description":3124,"labels":3125,"number":3130,"owner":3027,"repository":3027,"state":3068,"title":3131,"updated_at":3132,"url":3133,"score":3134},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚 -->\r\n\r\n### Is your feature request related to a problem? Please describe.\r\nMicro-frontend\r\n\r\n\u003C!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\r\n\r\n### Describe the solution you'd like\r\n\r\nHow about we warp the rendering and destruction process of the page into functions, and provide these functions to the users so they could decide when to call these functions. We only need to change the [client.js template](https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/template/client.js) a little bit to implement this.\r\n\r\n\u003C!-- A clear and concise description of what you want to happen. Adding some code examples would be neat! -->\r\n\r\n### Describe alternatives you've considered\r\n\r\nNone\r\n\r\n\u003C!-- A clear and concise description of any alternative solutions or features you've considered. -->\r\n\r\n### Additional context\r\n\r\nNone\r\n\r\n\u003C!-- Add any other context or screenshots about the feature request here. -->\r\n\r\nHi, nuxt maintainers. Thank you for building such a great community!\r\n\r\nI'm trying to build an application using micro-frontend. I have found some solutions like [single-spa](https://single-spa.js.org/) and [qiankun](https://qiankun.umijs.org/guide). (P.S. qiankun is based on single-spa)\r\n\r\nBoth of them require sub-applications to provide some lifecycle functions.\r\n\r\nSay `qiankun` as an example : it needs sub app to provide:\r\n1. A `mount` function used to render pages so that `qiankun` can control when the sub app is mount.\r\n2. A `unmount` function used to destroy instance so that `qiankun` can control when the sub app instance is close.\r\n\r\nWe can easily do it in `Vue` cause we could define when and how we create, mount or unmount the `vue instace`(see also the [example](https://qiankun.umijs.org/guide/tutorial#vue-micro-app)).\r\n\r\nIn `nuxt`, it's another case. These processes done by `nuxt` behind the scenes, so it's impossible to use `qiankun` with `nuxt` without changing the nuxt file. \r\n\r\nSo I have a proposal: how about we warp the rendering and destruction process of the page into functions, providing to the users so they could decide when to call these functions. We only need to change the [client.js template](https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/template/client.js) a little bit to implement this.\r\n\r\nSee also the implemention of the nuxt module [nuxt-micro-frontend](https://github.com/FEMessage/nuxt-micro-frontend/blob/dev/lib/client.js) with a change of `client.js`.\r\n\r\nWDYT?",[3126,3127],{"name":3050,"color":3051},{"name":3128,"color":3129},"2.x","d4c5f9",8970,"What about support for micro-frontend framework with a little change of client.js template","2024-06-14T16:02:35Z","https://github.com/nuxt/nuxt/issues/8970",0.7755229,{"description":3136,"labels":3137,"number":3141,"owner":3027,"repository":3027,"state":3068,"title":3142,"updated_at":3143,"url":3144,"score":3145},"As this project is becoming more and amazing, it will be great to set/evolve the vision. I would suggest adding roadmap to see what we can expect for 1.0 and even beyond.\r\n\r\nI have already seen references for \r\n\r\n- Middleware (v1.0)\r\n- PWA\r\n- Apollo/GraphQL integration\r\n- Typescript support\r\n- Websocket support\r\n- java via Nashorn (separate project)\r\n- auth modules for various auth providers inc oauth support ( [passport.js ?](http://passportjs.org/) )\r\n- integration patterns with more services\r\n- direct deploy to number of clouds (Aws, Google Cloud)\r\n- Analytics plugins\r\n- patterns library\r\n- Nuxt api\r\n\r\nProbably I missed a lot. But even if some of these could be implemented, it would be fantastic.\r\n\r\nAlso, I am sure with community effort even wider and more exciting vision can be built and a roadmap could be published for realising that vision.\r\n\r\nSo let's add version history and roadmap.\r\n\r\nThanks\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c109\">#c109\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3138,3140],{"name":3021,"color":3139},"cc317c",{"name":3128,"color":3129},132,"roadmap?","2023-01-18T15:38:30Z","https://github.com/nuxt/nuxt/issues/132",0.7793481,["Reactive",3147],{},["Set"],["ShallowReactive",3150],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9osdFCc6wvxKXKXI6CQR8k4oeJe4eHlzsjRrvZJ3Txg":-1},"/nuxt/ui/2438"]