\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_",[3186,3189],{"name":3187,"color":3188},"feature","A27AF6",{"name":3174,"color":3161},3094,"[RFP] The Inputs Update","2025-07-31T02:45:34Z","https://github.com/nuxt/ui/issues/3094",0.7533484,{"description":3196,"labels":3197,"number":3205,"owner":3149,"repository":3149,"state":3151,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v14.18.2`\r\n- Nuxt Version: `3.0.0-rc.4-27605536.8c2c80e`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nPlease see reproduction example here: https://github.com/sppmstar/nuxt-3-module-layout-vite-bug\n\n### Describe the bug\n\nWhen adding a style block to a custom layout in a Nuxt 3 module, i get the following error:\r\n\r\n\u003Cimg width=\"917\" alt=\"Screen Shot 2022-06-29 at 14 44 59\" src=\"https://user-images.githubusercontent.com/81262028/176529465-2a348f3e-e81c-4e18-855f-aabb8617962d.png\">\r\n\r\nIf I remove the \u003Cstyle> block, it works fine. See here: https://github.com/sppmstar/nuxt-3-module-layout-vite-bug/blob/master/src/layouts/custom-layout.vue#L7-L11\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3198,3201,3202],{"name":3199,"color":3200},"workaround available","11376d",{"name":3171,"color":3172},{"name":3203,"color":3204},"upstream","E8A36D",14245,"Nuxt 3 Module custom layout style issue","2024-06-30T11:10:31Z","https://github.com/nuxt/nuxt/issues/14245",0.7587446,{"description":3211,"labels":3212,"number":3217,"owner":3149,"repository":3150,"state":3218,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### Description\n\nHello, \n\nI started using nuxt ui pro 3 in beta version, and we get the component pro. But you had some nice feature like pricingtable and we need it to populate our figma for our project. Where can we refind it ? ",[3213,3214],{"name":3146,"color":3147},{"name":3215,"color":3216},"nuxt/ui-pro","00dc82",4212,"closed","Where can i find the update of the components for FIGMA ?","2025-05-23T15:48:38Z","https://github.com/nuxt/ui/issues/4212",0.6712734,{"description":3224,"labels":3225,"number":3227,"owner":3149,"repository":3150,"state":3218,"title":3174,"updated_at":3228,"url":3229,"score":3230},"The development is ongoing on the default branch of this repository: https://github.com/nuxt/ui.\n\n---\n\nA lot has changed since `@nuxt/ui` was made open-source (May 2023), so the plan here is to rewrite every component from scratch alongside their config.\n\nI'll post regular updates on this issue and on https://twitter.com/benjamincanac.\n\n## Documentation\n\nhttps://ui3.nuxt.dev\n\n## Roadmap (Nov 20, 2024)\n\n- [x] Finish the migration to `reka-ui@alpha` on `@nuxt/ui` & `@nuxt/ui-pro` #2448\n- [x] Write the docs for implemented `@nuxt/ui-pro` components\n- [x] Finish `@nuxt/ui-pro` components\n- [x] Make Nuxt UI Pro v3 work with Vue like Nuxt UI https://github.com/nuxt/ui-pro/pull/742\n- [ ] Implement new components in `@nuxt/ui` like\n - [x] `Calendar` #2618\n - [ ] `InputDate` #2524\n - [x] `Tree` #3180\n - [x] `Stepper` #2733\n- [x] Migrate all the Nuxt UI Pro templates\n - [x] Starter\n - [x] Landing\n - [x] Docs\n - [x] SaaS https://github.com/nuxt-ui-pro/saas/pull/86\n - [x] Dashboard https://github.com/nuxt-ui-pro/dashboard/pull/86\n- [ ] Build the Nuxt UI docs marketing pages\n - [x] Landing\n - [x] Figma\n - [x] Pro -> Landing\n - [x] Pro -> Pricing\n - [x] Pro -> Templates\n - [x] Pro -> Activate\n - [ ] Releases\n- [x] Write migration guide https://ui3.nuxt.dev/getting-started/migration\n- [x] Release `@nuxt/ui` & `@nuxt/ui-pro` officially once `tailwindcss` and `reka-ui` are released\n- [x] Migrate all the Nuxt apps (nuxt.com, image.nuxt.com, eslint.nuxt.com, devtools.nuxt.com, fonts.nuxt.com, hub.nuxt.com, nuxt.studio, etc.)\n- [ ] Implement new `@nuxt/ui` & `@nuxt/ui-pro` components\n- [ ] Create new templates like Changelog, Portfolio, etc. \n\n## Breaking Changes\n\nThe biggest change is the switch to `tailwind-variants`, this will cause lots of breaking changes if you've used the `ui` prop or `app.config.ts` to override the config. I apologize in advance for this but I strongly believe this will be beneficial and will bring consistency across all components.\n\n> At the beginning the config was split in many keys for the same div to give more flexibility, but since then we introduced `tailwind-merge` which now allows us to group those keys together, this is a good opportunity to clean the whole thing. \n\nThe config will now have a `slots` amongst other keys that will specifically target dom nodes. The `ui` prop will only allow you to target those slots.\n\nThese changes alongside the refactor of all components will also improve the types, the `app.config.ts` and `ui` props are now perfectly typed, as well as all components `props`, `slots`, `emits` and `expose`.\n\n> Feel free to comment on this if you have any ideas for the next major.\n\n```[tasklist]\n### Components\n- [x] Accordion\n- [x] Alert\n- [x] Avatar\n- [x] AvatarGroup\n- [x] Badge\n- [x] Breadcrumb\n- [x] Button\n- [x] ButtonGroup\n- [x] Card\n- [x] Carousel\n- [x] Checkbox\n- [x] Chip\n- [x] Collapsible\n- [x] CommandPalette\n- [x] Container\n- [x] ContextMenu\n- [x] Drawer\n- [x] DropdownMenu (Dropdown)\n- [x] Form\n- [x] FormField (FormGroup)\n- [x] Icon\n- [x] Input\n- [x] InputMenu\n- [x] Kbd\n- [x] Link\n- [x] Modal\n- [x] NavigationMenu (HorizontalNavigation/VerticalNavigation)\n- [x] Pagination\n- [x] Popover\n- [x] Progress\n- [x] Provider\n- [x] RadioGroup\n- [x] Select\n- [x] SelectMenu\n- [x] Separator (Divider)\n- [x] Skeleton\n- [x] Slideover\n- [x] Slider (Range)\n- [x] Table\n- [x] Tabs\n- [x] Textarea\n- [x] Toast (Notification)\n- [x] Switch (Toggle)\n- [x] Tooltip\n```\n",[3226],{"name":3160,"color":3161},1289,"2025-07-17T12:55:11Z","https://github.com/nuxt/ui/issues/1289",0.7309581,{"labels":3232,"number":3239,"owner":3149,"repository":3149,"state":3218,"title":3240,"updated_at":3241,"url":3242,"score":3243},[3233,3236],{"name":3234,"color":3235},"3.x","29bc7f",{"name":3237,"color":3238},"pending triage","E99695",14196,"How does Nuxt2 upgrade to NUXT3?","2023-01-19T17:42:47Z","https://github.com/nuxt/nuxt/issues/14196",0.7424694,{"labels":3245,"number":3252,"owner":3149,"repository":3149,"state":3218,"title":3253,"updated_at":3254,"url":3255,"score":3256},[3246,3249],{"name":3247,"color":3248},"enhancement","8DEF37",{"name":3250,"color":3251},"2.x","d4c5f9",10448,"Will Nuxt 2 continue to get updates?","2023-01-22T15:52:59Z","https://github.com/nuxt/nuxt/issues/10448",0.74379057,{"description":3258,"labels":3259,"number":3262,"owner":3149,"repository":3149,"state":3218,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### What problem does this feature solve?\r\n\r\nNuxt was created before Vue CLI 3 and Nuxt generator does not have the flexibility and plug-in model of the CLI3 that lets add/remove/modify features in your existing project, for example, add TypeScript or a CSS library in the project as an after-though. It also provides a nice UI for modifying the plugins in your web browser. I believe Nuxt should take advantage of this architecture without reinventing the wheel. The fact that I cannot use CLI3 features in a nuxt application discourages me from using nuxt, instead if nuxt was provided as a CLI3 plugin to add nuxt structure and features on top of a vue project (maybe as a sub-structure or module if that makes it easier) then I could easily choose to use Nuxt, because I know I will have control over it through CLI3 plugin system to upgrade or even remove it if I want to. In fact I believe this should be the primary way supported to install Nuxt.\r\n\r\nThere looks to be an attempt on doing this with [vue-cli-plugin-nuxt-starter-template](https://github.com/andoshin11/vue-cli-plugin-nuxt-starter-template) by @andoshin11 but it doesn't seem to be actively maintained.\r\n\r\n### What does the proposed changes look like?\r\n\r\nYou run a Vue CLI 3 command like `vue add nuxt` and it will add nuxt structure and build to your existing VueJS project.\r\n\r\n\u003C!--cmty-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9613\">#c9613\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3260,3261],{"name":3247,"color":3248},{"name":3250,"color":3251},6199,"Provide Nuxt as a vue-cli 3 plugin","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/6199",0.7454656,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fshRwiltNI9oIBjbQgOJg003V-jMAb5uXCj1Ydy3X-_c":-1},"/nuxt/ui/4827"]