\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_",[3019,3022],{"name":3020,"color":3021},"feature","A27AF6",{"name":3023,"color":3024},"v3","49DCB8",3094,"nuxt","ui","open","[RFP] The Inputs Update","2025-07-31T02:45:34Z","https://github.com/nuxt/ui/issues/3094",0.71490085,{"description":3034,"labels":3035,"number":3038,"owner":3026,"repository":3027,"state":3039,"title":3023,"updated_at":3040,"url":3041,"score":3042},"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",[3036],{"name":3037,"color":3024},"release",1289,"closed","2025-07-17T12:55:11Z","https://github.com/nuxt/ui/issues/1289",0.69353324,{"description":3044,"labels":3045,"number":3049,"owner":3026,"repository":3027,"state":3039,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### Description\n\nHello, I have read that with the Vercel and Nuxt collaboration that Nuxt UI/Pro will be licence free relatively soon and an new version will be create `v4`. My questions is, can we alreay make v3 license free because of this changes or do we need to wait for v4?\n\nThank you",[3046],{"name":3047,"color":3048},"question","d876e3",4595,"Nuxt UI Pro - Vercel and licence free on build?","2025-07-26T11:28:35Z","https://github.com/nuxt/ui/issues/4595",0.70390713,{"description":3055,"labels":3056,"number":3063,"owner":3026,"repository":3026,"state":3039,"title":3064,"updated_at":3065,"url":3066,"score":3067},"Hi!\n\nIt seems that the new **shared folder** feature annouced on the [Nuxt Blog](https://nuxt.com/blog/v3-14#shared-folder-for-code-and-types-shared-with-clientserver) requires Nuxt V4 although the post makes it seem like it is also available for V3.\n\nMaybe either the feature should be backported to V4 or the blog post should be updated accordingly?",[3057,3060],{"name":3058,"color":3059},"documentation","5319e7",{"name":3061,"color":3062},"good first issue","fbca04",29960,"Shared folder - Nuxt Blog annoucement","2024-12-10T22:59:05Z","https://github.com/nuxt/nuxt/issues/29960",0.7072243,{"description":3069,"labels":3070,"number":3073,"owner":3026,"repository":3027,"state":3039,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Description\n\nHello! I have few(5) projects that uses v2 version of Nuxt UI, and i am also a huge fun of this awesome UI library. Now i dont know what to do - migrate to v3 or continue use v2.\nwhat your plans for v2, and what about migration to v3? is there will be automatic, semi-automatic migration flow or all code we need to rewrite by themselves.\nAnyway, for all new projects i already use v3 and it is awesome!)",[3071,3072],{"name":3047,"color":3048},{"name":3023,"color":3024},2990,"migration to v3 or v2 support","2025-01-06T11:17:52Z","https://github.com/nuxt/ui/issues/2990",0.7093152,{"description":3079,"labels":3080,"number":3090,"owner":3026,"repository":3026,"state":3039,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Describe the feature\n\nRecently I've been trying to configure my Nuxt project to have globally available types. I couldn't find any useful info in the docs nor in the issues or discussions. \r\n\r\nThis resulted in me creating #22209 and it turned out that Vue has support for global type declaration files: \r\nhttps://github.com/vuejs/core/blob/a3dddd62059f4a7a762046c1e7f01485b96e737d/packages/compiler-sfc/src/compileScript.ts#L75-L79\r\n\r\nHowever Nuxt does not allow users to specify this setting in the vite schema:\r\nhttps://github.com/nuxt/nuxt/blob/61146aacaffa24772b1c2107ef623f2ab202141c/packages/schema/src/config/vite.ts#L49-L57\r\n\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3081,3084,3087],{"name":3082,"color":3083},"types","2875C3",{"name":3085,"color":3086},"3.x","29bc7f",{"name":3088,"color":3089},"upstream","E8A36D",22220,"Support global type definition files","2024-10-08T03:13:57Z","https://github.com/nuxt/nuxt/issues/22220",0.7176058,{"description":3096,"labels":3097,"number":3100,"owner":3026,"repository":3026,"state":3039,"title":3101,"updated_at":3102,"url":3103,"score":3104},"(Collabrated with @Atinux @danielroe @clemcode to set new structure)\r\n\r\nNotes:\r\n - Items in (...) indicate old name.\r\n - I've removed [new] sections to make it a fast structure refactor\r\n\r\n----\r\n\r\n- **Landing**\r\n- **Getting Started**\r\n - Intro (Concepts/What is Nuxt)\r\n - Installation (Getting Started>Quick Start)\r\n - Views (Features>Views)\r\n - Assets & Styles (features> assets)\r\n - SEO & Meta (Features>Head)\r\n - Data Fetching (Features>Data Fetching)\r\n - State Management (Features State Management)\r\n - Error Handling (Features>Error Handling)\r\n - Testing (Features/Testing)\r\n - Deployment (Deploy/* merged)\r\n - Upgrade guide\r\n - Upgrade from Nuxt 2 (Getting Started>Migration Guide)\r\n - Edge Channel\r\n- **Guide**\r\n - Key Concepts\r\n - Core Architecture (Advanced > How Nuxt Works + Life Cycle Hooks)\r\n - Auto Imports (Concepts > Auto Imports)\r\n - Development in Nuxt (Concepts/Vue.js Development)\r\n - Modules (Features/Modules)\r\n - Rendering Modes (Concepts > Rendering Modes)\r\n - ES Modules (Advanced > ES Modules)\r\n - **Server** (Features/Server Routes)\r\n - Directory structure\r\n - [auto-loaded files and dirs]\r\n - Module Guide\r\n - Get started (module author guide)\r\n - Nuxt Kit\r\n- **API Reference**\r\n - Composables\r\n - Components\r\n - Utils\r\n - **Advanced**\r\n - **Lifecycle Hooks**\r\n - **Kit utils**\r\n - Commands\r\n - Configuration\r\n- **Examples**\r\n - [categories]\r\n- **Community**\r\n - **Getting help**\r\n - **Reporting bugs**\r\n - **Contribution**\r\n - **Roadmap**",[3098,3099],{"name":3058,"color":3059},{"name":3085,"color":3086},14700,"Docs structure update","2023-01-19T17:39:01Z","https://github.com/nuxt/nuxt/issues/14700",0.71867657,{"description":3106,"labels":3107,"number":3112,"owner":3026,"repository":3026,"state":3039,"title":3113,"updated_at":3114,"url":3115,"score":3116},"## Motivation\r\n\r\nVue is a very international community with a lot of presence in non-english regions like China.\r\n\r\n- Many community members have proposed their help here https://github.com/nuxt/nuxt/discussions/16054\r\n- China have a (non-official ?) Chinese version of the Nuxt docs https://github.com/nuxt/nuxt/discussions/16208 : https://nuxt.com.cn/\\\r\n- A Russian translation has been discussed https://github.com/nuxt/nuxt/discussions/17351\r\n- A Ukrainian translation have been discussed https://github.com/nuxt/nuxt/issues/19926\r\n\r\nFormkit recently released an AI translation for their website docs https://formkit.com/ in 4 languages. \r\n\r\nWe could take a similar approach and combine it with the existing community translations.\r\nIn my opinion, an AI approach needs to be compatible with existing contributions, and manual modifications.\r\n\r\n## Implementation idea\r\n\r\n*Disclaimer: I'm sharing some of my thoughts about how we could build such a system, to gauge community interest in doing so. Suggestion and feedback would be very appreciated!*\r\n\r\nWe would use i18n for the docs website to handle the language strings (related docus issue https://github.com/nuxt-themes/docus/issues/770)\r\nThen to keep the translations in sync with the english source, we could run logic (maybe within the CI), that is triggered when english docs gets merged in nuxt/nuxt, and automatically open PRs for each language with a LLM translation inserted at the right location. \r\nWith such a system, the Nuxt community/team can review the LLM output and modify it before merging it for their language. \r\nAll new additions to the docs must be done in English, so that they are reflected anywhere.\r\nIf translations PRs are an issue for maintainers, we could move all of this to another repo `nuxt-international` or something.\r\n\r\nMany of the Nuxt/Unjs team members already speak 2 or more languages, so we could start out with these languages.\r\nIf this system is successful, it can be expanded and applied to other things, such as the UnJS ecosystem, or integrated with docus\r\n\r\n### Create entire translations from scratch\r\n\r\nWhile working from human written translation is more accurate, we could also experiment with entirely AI written translations. We could build a tool that translates all markdown docs content from the english source into a new language.\r\n\r\n## Bonus\r\n\r\nLook at worldwide trends for Nuxt over the last year : https://trends.google.com/trends/explore?q=nuxt,nuxtjs,nuxt.js&hl=en-GB\r\n\r\nInterestingly enough, there's more search interest for Nuxt in China than in english speaking countries.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/98146ec6-c6d7-479d-afb9-bcb7ee13bf4f\">\r\n\r\nIn fact, the anglosphere rank significantly lower than other areas.\r\n\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] 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).",[3108,3109],{"name":3058,"color":3059},{"name":3110,"color":3111},"discussion","538de2",21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.7238259,{"labels":3118,"number":3121,"owner":3026,"repository":3026,"state":3039,"title":3122,"updated_at":3123,"url":3124,"score":3125},[3119,3120],{"name":3058,"color":3059},{"name":3085,"color":3086},10926,"Documentation Progress","2023-01-19T14:32:52Z","https://github.com/nuxt/nuxt/issues/10926",0.7246934,{"description":3127,"labels":3128,"number":3130,"owner":3026,"repository":3026,"state":3039,"title":3131,"updated_at":3132,"url":3133,"score":3134},"Explain about the story for the creation of Nuxt 3, from the initial work on Vue 3 to a complete opportunity to shape a strong fondation for the future of Nuxt and the Vue ecosystem.\n\nNuxt 3 has some breaking changes, but this has made carefully chosen in order to have:\n- a faster framework (Webpack 5 and Vite)\n- Hybrid rendering with Nitro (and working in service workers)\n- lighter with optional pages\n- more intuitive (App.vue)\n- Universal JS (explain the initiative of unjs project)\nEtc.\n\nIt would like also to showcase a timeline of the work we have done, by help one this @pi0 @danielroe to gather the information is much appreciated.",[3129],{"name":3085,"color":3086},11065,"Docs: The Story 🐣🕊","2023-01-19T14:49:42Z","https://github.com/nuxt/nuxt/issues/11065",0.725404,["Reactive",3136],{},["Set"],["ShallowReactive",3139],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fThhl1YJ6YGsLReULpxNIqZn1WLHZbkxT0F7J-7Ea5us":-1},"/nuxt/ui/4488"]