`\nDoesn't result in the test id being applied.\n\nThis can probably be fixed by enabling (some more) fallthrough attributes.\nhttps://vuejs.org/guide/components/attrs\n\nThanks for the work on this project!\n\n### Additional context\n\n_No response_",[3208,3209],{"name":3140,"color":3141},{"name":3146,"color":3147},4679,"Allow Fallthrough Attributes","2025-08-17T13:45:19Z","https://github.com/nuxt/ui/issues/4679",0.7426933,{"description":3216,"labels":3217,"number":3220,"owner":3149,"repository":3150,"state":3185,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Description\n\nHello,\n\nrecently I started to use nuxt ui. I don't understand why some of the types are exposed (exported) while other not. For instance AuthFormField. When I try example provided in the documentation my IDE complains that the array assigned to the fields property \"is not assignable to type AuthFormField[]\". Sure code runs, but still.\n\nThe type is defined in the AuthForm.vue.d.ts file but never exported. Is it by design?\n\nBest regards,\nAleksander\n\n",[3218,3219],{"name":3170,"color":3171},{"name":3143,"color":3144},4797,"AuthFormField type not exported","2025-08-25T14:00:20Z","https://github.com/nuxt/ui/issues/4797",0.74974936,{"description":3226,"labels":3227,"number":3234,"owner":3149,"repository":3149,"state":3185,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Describe the feature\n\nHi, I understand such tag `\u003Cscript id=\"__NUXT_DATA__\" ... />` is mandatory for hydration and client-side rendering, but I reckon showing raw values can cause security pitfall. I ran into a situation where secret values needed during client-side rendering.\r\n\r\nIt would be great if nuxt provides an encryption feature like below.\r\n\r\n```\r\n// nuxt.config.ts\r\nexport default defineNuxtConfig({\r\n nuxtData: {\r\n encryption: {\r\n type: 'AES',\r\n key: 'secret',\r\n }\r\n }\r\n});\r\n```\n\n### Additional information\n\n- [ ] 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).",[3228,3231],{"name":3229,"color":3230},"3.x","29bc7f",{"name":3232,"color":3233},"pending triage","E99695",24475,"support `__NUXT_DATA__` encryption from nuxt config file","2023-11-27T09:35:39Z","https://github.com/nuxt/nuxt/issues/24475",0.7568088,{"description":3240,"labels":3241,"number":3243,"owner":3149,"repository":3150,"state":3185,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nHi,\n\nWould it be possible to add an export of all components ?\n\nSomething like:\n\n```js\nexport * from './components'\n```\n\n### Additional context\n\nI'm trying to display a form field according to its value type (ex: boolean => checkbox, number => range ...).\n\nSadly, it looks like in composition API, one cannot use string for `\u003Ccomponent>` `:is` prop.\n\n```vue\n\u003Ctemplate>\n \u003C!-- This doesn't work -->\n \u003Ccomponent :is=\"typeof value === 'boolean' ? 'u-checkbox' : 'u-input'\" />\n\u003C/template>\n```\n\nApparently, you have to pass the component itself, but I'm unable to import components from Nuxt UI:\n\n```vue\n\u003Cscript setup>\n// This doesn't work\nimport { UCheckbox, UInput } from '@nuxt/ui';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Ccomponent :is=\"typeof value === 'boolean' ? UCheckbox : UInput\" />\n\u003C/template>\n```\n\nI can use `v-if` as a workaround, but it forces me to duplicate a lot of props (class, listeners, model ...) on each component.",[3242],{"name":3140,"color":3141},2891,"Export of every components","2025-01-13T16:32:50Z","https://github.com/nuxt/ui/issues/2891",0.75799435,{"description":3249,"labels":3250,"number":3256,"owner":3149,"repository":3149,"state":3185,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: pnpm@8.9.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-4cyshx?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\ninput Use v-model two-way binding, when change the v-model to :value, the two-way binding is still effective, need to refresh the page, then it will be normal.\r\n\r\n### Logs\r\n\r\n_No response_",[3251,3252,3253],{"name":3229,"color":3230},{"name":3232,"color":3233},{"name":3254,"color":3255},"needs reproduction","FBCA04",23688,"input Use v-model bidirectional binding hot update exception","2023-10-17T08:33:12Z","https://github.com/nuxt/nuxt/issues/23688",0.7604186,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$furlR3bkSwG34uVP9TrHmGVFXLqSA1po8_pIY7vv7Y3E":-1},"/nuxt/ui/3430"]