\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_",[3184,3187],{"name":3185,"color":3186},"feature","A27AF6",{"name":3143,"color":3144},3094,"[RFP] The Inputs Update","2025-07-31T02:45:34Z","https://github.com/nuxt/ui/issues/3094",0.7291879,{"description":3194,"labels":3195,"number":3200,"owner":3146,"repository":3146,"state":3201,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### What problem does this feature solve?\n\nCurrently, Nuxt.js does not have a way to create actions to be done only on the client.\nIt is possible to implement it using plugins and middleware, but it will be implemented with a different interface from nuxtServerInit.\n\nAlso, in SPA mode there is no equivalent of nuxtServerInit.\n\nIn order to solve this problem, I would like to add nuxtServerInit for clients.\n\n### What does the proposed changes look like?\n\nI implemented it as a module of Nuxt.js. However, I want Nuxt.js core to have nuxtClientInit.\n\nhttps://github.com/potato4d/nuxt-client-init-module\n\n- - -\n\nAlthough it was written that it is advancing the implementation before, is there any plan to implement it?\n\nIf possible, I would like to collaborate on implementation.\n\nhttps://github.com/nuxt/nuxt.js/issues/1857#issuecomment-336874401\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/c7801\">#c7801\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3196,3197],{"name":3168,"color":3169},{"name":3198,"color":3199},"2.x","d4c5f9",3938,"closed","Implementation of nuxtClientInit Action","2023-01-22T15:50:41Z","https://github.com/nuxt/nuxt/issues/3938",0.70036197,{"description":3207,"labels":3208,"number":3214,"owner":3146,"repository":3147,"state":3201,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Description\n\n🙏 First of all, thank you to the Nuxt UI team for your outstanding contributions!\n\nNuxt UI has greatly improved the developer experience for building modern Nuxt applications.\n\n---\n\nDescription\n\nCurrently, nuxt/ui provides a powerful set of UI components and form elements, but it lacks a built-in dynamic schema-form system. In many enterprise applications, we spend a lot of repetitive time writing similar form templates and CRUD logic.\n\nI propose adding a \u003Cschema-form> component, similar to [Ant Design ProComponents Schema Form](https://procomponents.ant.design/en-US/components/schema-form), to help developers quickly build dynamic forms with minimal boilerplate.\n\nMotivation\n\t•\tReduce repetitive code for standard CRUD forms.\n\t•\tCentralize form configuration into JSON schema.\n\t•\tAutomatically handle form rendering, validation, and API requests.\n\t•\tSimplify maintenance and improve developer productivity for admin panels and back-office tools.\n\n---\nProposed API\n\nA possible schema-form component interface could be:\n\n```vue\n\u003CSchemaForm\n :schema=\"{\n title: 'User Info',\n mode: 'create', // or 'update'\n api: {\n detail: '/api/user/detail',\n create: '/api/user/create',\n update: '/api/user/update'\n },\n fields: [\n { label: 'Username', name: 'username', component: 'input', rules: [{ required: true }] },\n { label: 'Email', name: 'email', component: 'input' },\n { label: 'Role', name: 'role', component: 'select', options: [\n { label: 'Admin', value: 'admin' },\n { label: 'User', value: 'user' }\n ]}\n ],\n initialValues: { role: 'user' }\n }\"\n @submit-success=\"onSubmit\"\n/>\n```\n---\nFeatures\n\t•\t✅ Schema-driven form rendering (fields, labels, validation, components)\n\t•\t✅ Auto-fetch detail API for edit mode\n\t•\t✅ Built-in submit to create/update APIs\n\t•\t✅ Support for u-input, u-select, u-date-picker, and custom components\n\t•\t✅ Works seamlessly with Nuxt UI design system\n\n---\n\nBenefits\n\t•\tSignificant reduction in repetitive CRUD form code\n\t•\tAligns with enterprise admin panel requirements\n\t•\tMatches developer experience from frameworks like Ant Design ProComponents\n\t•\tMakes Nuxt UI more competitive for dashboard/admin scenarios\n\n---\n\nAlternatives\n\nRight now, developers must:\n\t•\tManually write each form template (using u-form, u-form-item, etc.)\n\t•\tHandle API fetching/submission manually with useFetch\n\t•\tDuplicate similar code across multiple CRUD pages\n\n---\n\nReferences\n\t•\tAnt Design ProComponents Schema Form: https://procomponents.ant.design/en-US/components/schema-form\n\n\n### Additional context\n\n_No response_",[3209,3211],{"name":3168,"color":3210},"a2eeef",{"name":3212,"color":3213},"triage","ffffff",4653,"[Feature Request] Add dynamic schema-form similar to Ant Design ProComponents Schema Form for reducing CRUD workload","2025-08-07T17:19:54Z","https://github.com/nuxt/ui/issues/4653",0.71335095,{"description":3220,"labels":3221,"number":3230,"owner":3146,"repository":3146,"state":3201,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Describe the feature\n\nRight now, you can't have client components as children of server components, but enabling this would enable a bunch of usful usecases.\r\n\r\nfor example I have a big website using nuxt, with mostly static content but also bit of interactive content (like accordions or toggles to hide and show content).\r\nServer components would allow me to not send the JS for most of my site to the client, greatly reducing time spend on script parsing and execution (hydration), but right now that would disallow me from using any interactive elements.\r\n(for reference, next.js supports this: https://beta.nextjs.org/docs/rendering/server-and-client-components#moving-client-components-to-the-leaves)\r\n\r\nI would imagine that the easiest way would be to enable server components to have slots and in the client somehow check if there is a client component slot present in the server component html.\r\nMaybe NuxtServerComponent needs to parse the html to find out where to inject the slots or we can store that info in the island response.\r\n\r\nI have a bunch of work time next week to dedicate to working on this, but I dont really know where to start, if anybody has any pointers where I can look or what the best approach would be, that would be appreciated, I am MiniDigger#3086 on discord.\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).",[3222,3223,3226,3229],{"name":3168,"color":3169},{"name":3224,"color":3225},"good first issue","fbca04",{"name":3227,"color":3228},"3.x","29bc7f",{"name":3174,"color":3175},19765,"support client interactivity within server components","2023-05-15T22:43:55Z","https://github.com/nuxt/nuxt/issues/19765",0.7152121,{"description":3236,"labels":3237,"number":3239,"owner":3146,"repository":3146,"state":3201,"title":3240,"updated_at":3241,"url":3242,"score":3243},"Hey guys, I came up with a pattern to allow me have routes defined externally, in a single file, rather than automatically by Nuxt. I understand this goes off the framework's philosophy, but I like the fact that you've made it possible. What's missing from the docs is just how easy it is to accomplish this.\r\n\r\n1. Create a pages/index.js file like so:\r\n\r\n```js\r\nmodule.exports = [\r\n {\r\n name: 'login',\r\n path: '/login',\r\n component: 'src/pages/auth/login.vue'\r\n }\r\n] \r\n```\r\n\r\n2. Add the following to `nuxt.config.js`:\r\n\r\n```js\r\nconst routes = require('./src/pages/index')\r\n\r\nmodule.exports = {\r\n ...\r\n router: {\r\n extendRoutes (nuxtRoutes, resolve) {\r\n nuxtRoutes.splice(0, nuxtRoutes.length, ...routes.map((route) => {\r\n return {\r\n ...route,\r\n component: resolve(__dirname, route.component)\r\n }\r\n }))\r\n }\r\n ...\r\n}\r\n```\r\n\r\nAnd there you have it: routes defined in a file. I know you can also specify a `chunkName` for each route, but that doesn't seem to do much for me. Should I be concerned?\r\n\r\nAnyhow, this is NOT an issue, just a documentation enhancement proposal.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7271\">#c7271\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3238],{"name":3198,"color":3199},3460,"A simple extendRoutes() pattern","2023-01-18T16:24:09Z","https://github.com/nuxt/nuxt/issues/3460",0.720232,{"labels":3245,"number":3248,"owner":3146,"repository":3146,"state":3201,"title":3249,"updated_at":3250,"url":3251,"score":3252},[3246,3247],{"name":3168,"color":3169},{"name":3227,"color":3228},13848,"add noscript support","2025-02-13T09:02:12Z","https://github.com/nuxt/nuxt/issues/13848",0.7243174,{"labels":3254,"number":3258,"owner":3146,"repository":3146,"state":3201,"title":3259,"updated_at":3260,"url":3261,"score":3262},[3255,3256,3257],{"name":3168,"color":3169},{"name":3227,"color":3228},{"name":3174,"color":3175},14628,"Define plugins with object syntax","2023-04-11T11:58:45Z","https://github.com/nuxt/nuxt/issues/14628",0.7250403,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPOMMq6d2NCMY7WENJPW-YAEo3XOZAmKCEH6Qv6o9Q4g":-1},"/nuxt/nuxt/20649"]