`, so they could be available in Page Component. Is it possible?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1696\">#c1696\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2871],{"name":2872,"color":2873},"2.x","d4c5f9",1894,"It's impossible to pass props from layout?","2023-01-18T15:42:46Z","https://github.com/nuxt/nuxt/issues/1894",0.679561,{"description":2880,"labels":2881,"number":2890,"owner":2862,"repository":2862,"state":2863,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\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\nhttps://stackblitz.com/edit/nuxt-starter-dskmfq?file=pages%2Findex.vue\n\n### Describe the bug\n\nPassing props to NuxtLayout stopped working after rc-13. Browser shows 2 warnings\r\n\r\n- Extraneous non-props attributes were passed to component but could not be automatically inherited because component renders fragment or text root nodes\r\n\r\n- Missing required prop \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2882,2883,2884,2887],{"name":2853,"color":2854},{"name":2859,"color":2860},{"name":2885,"color":2886},"bug","d73a4a",{"name":2888,"color":2889},"🔨 p3-minor","FBCA04",15578,"Cannot pass props to NuxtLayout","2024-04-30T08:29:37Z","https://github.com/nuxt/nuxt/issues/15578",0.6864765,{"description":2896,"labels":2897,"number":2904,"owner":2862,"repository":2862,"state":2863,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Environment\n\n### Nuxi 3.6.1 \r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: runtimeConfig, app, css, modules, plugins, content, googleFonts, devtools\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.8.0, @nuxt/content@2.7.0, @nuxt/image@1.0.0-rc.1, @nuxtjs/google-fonts@3.0.1\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nI have tried to access the categories and productName but couldn't. Here is the screenshot of my code. \r\n\r\n\u003Cimg width=\"1629\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/33604077/726a9c2b-cf4b-478c-9b8e-ecc53b7a7614\">\r\n\n\n### Describe the bug\n\nI have tried to access the categories and productName but couldn't. Here is the screenshot of my code. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2898,2899,2902],{"name":2859,"color":2860},{"name":2900,"color":2901},"pending triage","E99695",{"name":2903,"color":2889},"needs reproduction",21976,"How to access Custom Props from child pages","2023-07-06T08:20:39Z","https://github.com/nuxt/nuxt/issues/21976",0.6921811,{"labels":2910,"number":2913,"owner":2862,"repository":2862,"state":2863,"title":2914,"updated_at":2915,"url":2916,"score":2917},[2911,2912],{"name":2853,"color":2854},{"name":2872,"color":2873},4430,"Multi-variant Nuxt App","2023-01-22T15:50:48Z","https://github.com/nuxt/nuxt/issues/4430",0.6929347,{"description":2919,"labels":2920,"number":2924,"owner":2862,"repository":2862,"state":2863,"title":2925,"updated_at":2926,"url":2927,"score":2928},"In Nuxt 3, we have introduced a new package `@nuxt/schema` that holds types, defaults, and documentation for all build-in configurations for Nuxt and from one source using [untyped](https://github.com/unjs/untyped). In comparation with Nuxt 2, these were separately maintained, often with inconsistencies. This new system is also designed to be future proof to be able to **manage configuration via UI** using generated (JSON)Schema files and also **runtime validation** to notice any usage issues.\r\n\r\nFor Nuxt modules, it is already possible to extend a typescript interface `ModuleOptions` to provide types, however it has same limitations of Nuxt 2 era. We have introduced new `schema` in new `@nuxt/kit` module definition system however it became unused.\r\n\r\nWith the introduction of Nuxt Layers, themes can also now require some specific configuration. Most importantly for configuring `runtimeConfig` and app config (either via `appConfig` or `app.config`)\r\n\r\nFor this, we can use the same tooling (untyped) as a built-in feature to allow providing custom configuration schemas from Nuxt layers and modules (also directly from a Nuxt project). Benefiting from most possibilities (note 1) we have already for core config.\r\n\r\nWe have made an experiment [nuxt-experiments/nuxt-config-schema](https://github.com/nuxt-experiments/nuxt-config-schema) that is now almost ready to be moved into a core experiment, allowing to make it better usable. It is possible to provide custom config schema for nuxt projects in different ways:\r\n\r\n- Using `nuxt.schema.ts` in main Nuxt project or a layer\r\n- Using `$schema` key in `nuxt.config`\r\n- Extend `nuxt.options.$schema` for modules\r\n- Extend schema using `schema:extend`, `schema:resolved` and `schema:beforeWrite` for modules (note 2)\r\n- Use `schema` in `defineNuxtModule` (recommended way for modules. also supports defaults)\r\n\r\nThe output will be in `.nuxt` directory and initially mainly usable for the Augmentation of types and custom purposes such as UI.\r\n\r\n\r\n**Notes:**\r\n\r\nnote 1: Since development and trial of the experimental module, one particularly important point we found is that, unlike the core usage, mixing schema with defaults is not a good practice. We can only merge schema after modules are setup and it is too late for them to **re**apply new defaults and do their config handling logic and also it makes it much harder to merge runtime configuration such as `app.config` since custom merger logic resides in runtime while schema is in the build-time namespace and merging strategy is different.\r\n\r\nnote 2: We have introduced two separate hooks. `extend`/`resolve` as main way to extend schema just after all modules are initialized and before core or any other place tries to use schema and another `beforeWrite` as last resort (less recommended) for when a module needs to extend schema based on build aftertifacts coming from webpack, rollup or nitro's rollup step and it mainly and only affects the written files.\r\n\r\n\r\n\r\n\r\n\r\n",[2921,2922,2923],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2859,"color":2860},15592,"Custom config schema","2023-04-07T01:47:49Z","https://github.com/nuxt/nuxt/issues/15592",0.6964961,{"description":2930,"labels":2931,"number":2937,"owner":2862,"repository":2938,"state":2863,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Description\n\nHi,\n\nBeing able to override the **non-slot** properties of the tv theme using the ui prop would be very handy.\n\nSometimes you don't want to override globally but just want a slightly different variation of a component. When trying to restyle variations it becomes quite tricky when you cant override anything other than the slots.\n\neg. if you wanted to override compoundVariants the only choice is to do it globally, which naturally effects all uses of that component.\n\nA use case here is the UNavigationMenu. Accurately restyling hover effects etc is tricky without being able to override the whole tv object.\n\nI was also thinking it would be nice to be able to define your own theme directory where you could define component tv objects which either replace or merge with the Nuxt ui versions.\n\nThanks\nLee\n\n### Additional context\n\n_No response_",[2932,2934],{"name":2853,"color":2933},"a2eeef",{"name":2935,"color":2936},"v3","49DCB8",3382,"ui","Add ability to override entire tv object from ui prop","2025-05-23T13:04:10Z","https://github.com/nuxt/ui/issues/3382",0.6970104,{"description":2944,"labels":2945,"number":2949,"owner":2862,"repository":2862,"state":2863,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Describe the feature\n\nI'm trying migrate my vue3 project to nuxt3, but find many problems.\r\nJust as below codes, nuxtPage cannot get its rendering component, but the router-view has such api to achieve it. \r\n\r\n```\r\n \u003Crouter-view :style=\"viewStyle\" v-slot=\"{ Component }\">\r\n \u003Ccomponent :is=\"Component\" />\r\n \u003C/router-view>\r\n \u003Crouter-view :style=\"viewStyle\" name=\"user\" v-slot=\"{ Component }\">\r\n \u003Ctransition appear name=\"slide\">\r\n \u003Ccomponent :is=\"Component\" />\r\n \u003C/transition>\r\n \u003C/router-view> \r\n```\r\nIn nuxt3 I cannot use nuxtPage to achieve the same effect of above codes.\r\nSeems NuxtPage neither get its rendering component nor add addtional style to its rendering component .\r\nHence need NuxtPage to get its rendering component to achieve the dynamic component feature in vue3. Thx!\r\n\r\n\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).",[2946,2947,2948],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2859,"color":2860},24670,"allow passing props directly to page via `\u003CNuxtPage>`","2023-12-14T04:13:01Z","https://github.com/nuxt/nuxt/issues/24670",0.69932353,{"description":2955,"labels":2956,"number":2959,"owner":2862,"repository":2862,"state":2863,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.1\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-voetqy-p6tmsz?file=components/VTestExtends.vue\r\n\r\n### Describe the bug\r\n\r\nIf you have\r\n\r\n```ts\r\nexport interface BaseProps {\r\n size?: 'small' | 'medium' | 'large';\r\n}\r\n\r\nimport { BaseProps } from 'baseProps'\r\ninterface Props extends BaseProps {\r\n variant?: 'primary' | 'secondary' | 'default';\r\n}\r\n```\r\n\r\nand try to define the properties using\r\n\r\n```ts\r\nconst props = withDefaults(defineProps\u003CProps>(), {\r\n size: 'medium',\r\n variant: 'default',\r\n});\r\n```\r\n\r\nOnly `variant` is picked up as property, `size` is not.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2957,2958],{"name":2859,"color":2860},{"name":2900,"color":2901},20370,"defineProps using an interface that extends a base interface does not pick up the props from the base interface","2023-04-18T18:04:21Z","https://github.com/nuxt/nuxt/issues/20370",0.6995735,{"description":2965,"labels":2966,"number":2968,"owner":2862,"repository":2938,"state":2863,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### 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.",[2967],{"name":2853,"color":2933},2891,"Export of every components","2025-01-13T16:32:50Z","https://github.com/nuxt/ui/issues/2891",0.7014899,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fcwrJ7DoLCZXcYOzqFIJw8wLSyiaezXD-xjy6a6Fycpg":-1},"/nuxt/ui/4148"]