\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_",[3034,3037],{"name":3035,"color":3036},"feature","A27AF6",{"name":3038,"color":3022},"v3",3094,"[RFP] The Inputs Update","2025-07-31T02:45:34Z","https://github.com/nuxt/ui/issues/3094",0.73091793,{"description":3045,"labels":3046,"number":3053,"owner":3024,"repository":3024,"state":3026,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Environment\n\n-----------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: pnpm@8.6.12\r\n- Builder: vite\r\n- User Config: nitro, modules, build\r\n- Runtime Modules: tdesign-vue-next/es/nuxt\r\n- Build Modules: -\n\n### Reproduction\n\nno links right now. \n\n### Describe the bug\n\nThe UI lib has a component called t-form.\r\n\r\nWhen I use in the app without pages dir, it runs and build correctly.\r\n\r\nWhen I use in the pages/index.vue with a client-only wrapped, it runs and build correctly.\r\n\r\nBut just in the pages/index.vue,didn't work in build mode.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3047,3050],{"name":3048,"color":3049},"bug","d73a4a",{"name":3051,"color":3052},"🔨 p3-minor","FBCA04",22563,"Cannot build project when use a UI component tdesign-vue-next","2024-11-19T16:20:27Z","https://github.com/nuxt/nuxt/issues/22563",0.7326472,{"description":3059,"labels":3060,"number":3067,"owner":3024,"repository":3024,"state":3026,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### Describe the feature\n\n## **Main issue:** \n\nIt's a fact, `Nuxt` / `Vue app` are leaking all application URL(s) on hydration because the full router is shipped to the client (this is by design for the `Vue Router`).\n\nProblem: This allows attackers to get the full scope of your application as soon as they get to the first page, enlarging the potential attack surface by leaking your secret admin dashboard or other hidden URL .\n\n_Note: With only `Vue app`, your application is fully rendered in the client, making even all API routes string available without even passing the `Sign in` page, but as `Nuxt` brings `SSR` with it, (and if you do not write monkey code) this should no longer be the case._\n\nNowadays, more and more people use `Nuxt` with an `ORM` like `Prisma`, making it a real pain in the ass to setup a multi repo for each part of your app (who want's to pay **7$/user** a month to share a `Prisma schema` private module on `npm` ?). \n\n### **The questions are:** \n1. \"How to have 1 repo to rule them all and avoid to spread or copy interdependencies and components between repositories\" \n> I'm tired of looking at this:\n> ```\n> Github repository list:\n> - myproject-api \u003C--- prisma.schema\n> - myproject-user-dashboard \u003C--- prisma.schema + components like buttons\n> - myproject-admin-dashboard \u003C--- prisma.schema + components like buttons\n> - myproject-landing \u003C--- prisma.schema + components like buttons\n> ```\n> I want this:\n> ```\n> Github repository list:\n> - myproject 🎉\n> ```\n\n2. \"How to hide the existence of some section of my application\"\n> Why should the user receive all data about other section of the application that he should not be sniffing around ? \n\n3. \"How to use 1 app for all section but keeping them isolated of each other\"\n> Would be great to keep 1 server to render my web app even if it spitted in multiple sections right?\n\n## **Actual partial solution:** \nBuild distinct apps for each section of your app. One for the client, one for the admin etc... using `.env` variables and the `nuxt.config.ts` file's `ignore` property:\n\n**Building the client app without ignore:** \n\n\n**Building the client app with ignore:**\n\n\n### **Partial solution conclusion:** \nThis solve question 1 and 2, but what about question 3 ? I'm finding myself having to handle `1 container` / `node process` per section of my app... It's better, but... I don't need that much granularity.\n\n## **Another solution (feature request):**\nTo avoid to build and host multiple different apps for each section of your project : \n- 1 app for the landing pages + sign in\n- 1 app for the client dashboard\n- 1 app for the admin dashboard\n- etc...\n\nIt would be great to specify sections of the app that **Nuxt** would generate and serve independent router for.\n\n**Example:** \n```\n/pages \n - /landing \u003C-- 1 router for this section\n - /user \u003C-- 1 router for this section\n - /admin \u003C-- 1 router for this section\n```\n\n**Could be setup this way:** \n```ts\nexport default defineNuxtConfig({\n routers: {\n landing: [\"/pages/*.vue\",\"/pages/landing/**\"], \n user: [\"/pages/user/**\"],\n admin: [\"/pages/admin1234/**\"]\n ...\n }\n});\n```\n\n**This would generate 3 independent routers.**\n1. If the user goes to the landing page on `/`, it would be serve with the `landing` router, hiding the `user` and `admin` routes.\n2. If the user goes to the landing page on `/user`, it would be serve with the `user` router, hiding the `landing` and `admin` routes\n3. If the user goes to the landing page on `/admin1234`, it would be serve with the `admin` router, hiding the `landing` and `user` routes\n\n### **Feature solution conclusion:** \nThis should keep the evil at bay.\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [x] 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).",[3061,3064],{"name":3062,"color":3063},"enhancement","8DEF37",{"name":3065,"color":3066},"discussion","538de2",29872,"split section of your app via independent routers","2024-11-20T16:23:53Z","https://github.com/nuxt/nuxt/issues/29872",0.73678815,{"description":3073,"labels":3074,"number":3076,"owner":3024,"repository":3025,"state":3077,"title":3038,"updated_at":3078,"url":3079,"score":3080},"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",[3075],{"name":3021,"color":3022},1289,"closed","2025-07-17T12:55:11Z","https://github.com/nuxt/ui/issues/1289",0.6769672,{"description":3082,"labels":3083,"number":3087,"owner":3024,"repository":3025,"state":3077,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Description\n\nHi !\nFirst of all great work. I love this Kit.\nBut I was wondering if this Nuxt UI Kit (pro version) can be used just in Vue ? Without having the while framework ?\nI possibly need to build an app with AdonisJS with intertia in front, without haveing front router etc. \nI would just have the Vue templating, and hopefully built thanks to this kit \n:)",[3084],{"name":3085,"color":3086},"question","d876e3",4062,"Can Nuxt UI Pro be used just with Vue, Without Nuxt ?","2025-05-04T17:27:57Z","https://github.com/nuxt/ui/issues/4062",0.6800045,{"description":3093,"labels":3094,"number":3099,"owner":3024,"repository":3025,"state":3077,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Description\n\nHello, my team is considering purchasing the enterprise version of UI Pro. We have a few questions regarding the license key though. We do not develop through GitHub so will that cause an issue with the lisence key and building our project, or is our GitHub username that is submitted for activation only for accessing the private repo? And if we are planning on adding more developers are we able to add them to our lisence later? Thank you!",[3095,3096],{"name":3085,"color":3086},{"name":3097,"color":3098},"pro","5BD3CB",4053,"[PRO] License and Repo questions for enterprise","2025-05-02T17:20:30Z","https://github.com/nuxt/ui/issues/4053",0.7155019,{"description":3105,"labels":3106,"number":3111,"owner":3024,"repository":3025,"state":3077,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Environment\n\nMy most sincere recommendation, I love Vue, Nuxt, Nuxtui, but the truth is that everything on the market is being made almost exclusively for React, including TailwindCSS, so I advise against having Pro, just the full Free UI and open-source, take it or leave it, you decide.\n\n### Version\n\n2.20.0\n\n### Reproduction\n\nnuxtui.com\n\n### Description\n\nMy most sincere recommendation, I love Vue, Nuxt, Nuxtui, but the truth is that everything on the market is being made almost exclusively for React, including TailwindCSS, so I advise against having Pro, just the full Free UI and open source, take it or leave it, you decide.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3107,3108],{"name":3048,"color":3049},{"name":3109,"color":3110},"triage","ffffff",4297,"yes ui, no ui-pro","2025-06-05T19:46:12Z","https://github.com/nuxt/ui/issues/4297",0.71888965,{"description":3117,"labels":3118,"number":3121,"owner":3024,"repository":3025,"state":3077,"title":3122,"updated_at":3123,"url":3124,"score":3125},"### 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!)",[3119,3120],{"name":3085,"color":3086},{"name":3038,"color":3022},2990,"migration to v3 or v2 support","2025-01-06T11:17:52Z","https://github.com/nuxt/ui/issues/2990",0.72306055,{"description":3127,"labels":3128,"number":3133,"owner":3024,"repository":3024,"state":3077,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### What problem does this feature solve?\n\nnuxt has a package 'devalue' forked from Rich Harris. It is licensed under the LIL License but Rich has just changed this to MIT (https://github.com/Rich-Harris/devalue/issues/21). My company requires packages to be of a certain license before they can be used and the LIL License is not on the approved list nor seems supported these days (even the website lillicense.org is down now).\n\nCan @nuxt/devalue's license be changed to reflect this on NPM?\n\n### What does the proposed changes look like?\n\n@nuxt/devalue being published to NPM under the MIT License\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\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/c9380\">#c9380\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3129,3130],{"name":3062,"color":3063},{"name":3131,"color":3132},"2.x","d4c5f9",5954,"Change @nuxt/devalue package license from LIL License","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/5954",0.7249628,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fiO3QnvPmNTSJH_vkGpCZnQBibs0h1I82I1yusm1HxgI":-1},"/nuxt/ui/4595"]