\n```\n\nThe `as` prop type could be retrieved from the RekaUI component prop type directly using something like this\n\n```ts\ninterface InputProps {\n as?: InstanceProps\u003Ctypeof Primitive>['$props']['as']\n // Other props...\n}\n```\n\nIs there a reason that eludes me as to why this was not done?\n\nIf this seems like a good idea, I'd be happy to submit a PR.\n\nCheers!",[3186,3189],{"name":3187,"color":3188},"question","d876e3",{"name":3190,"color":3191},"v3","49DCB8",3068,"ui","[v3] `as` props typing","2025-01-10T17:28:25Z","https://github.com/nuxt/ui/issues/3068",0.7585549,{"description":3199,"labels":3200,"number":3205,"owner":3159,"repository":3193,"state":3161,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: -\n- CLI Version: 3.21.1\n- Nitro Version: -\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/nuxt/starter/tree/ui3\n\n### Description\n\nTested both with\n1. the official [nuxt ui v3 starter template](https://github.com/nuxt/starter/tree/ui3)\n2. Following the manual installation steps outlined in https://ui3.nuxt.dev/getting-started/installation/nuxt#use-our-nuxt-starter\n\nAfter a fresh install of the nuxt ui3 starter project (cd7e386) as instructed by the [nuxt documentation](https://ui3.nuxt.dev/getting-started/installation/nuxt#use-our-nuxt-starter), spinning up the dev-server yields errors, rendering the project unusable. Tried with node 20 and 22. Both times, the following error appears:\n\n```\n ERROR Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type. 2:44:13 PM\nIf this previously worked in 3.2, you can instruct the compiler to ignore this extend by adding /* @vue-ignore */ before it, for example:\n\ninterface Props extends /* @vue-ignore */ Base {}\n\nNote: both in 3.2 or with the ignore, the properties in the base type are treated as fallthrough attrs at runtime.\n\n/Users/\u003Csnip>/node_modules/@nuxt/ui/dist/runtime/components/Button.vue\n63 | \n64 | const loadingAutoState = ref(false)\n65 | const formLoading = inject\u003CRef\u003Cboolean> | undefined>(formLoadingInjectionKey, undefined)\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^\n66 | \n | ^\n67 | async function onClickWrapper(event: MouseEvent) {\n | ^^^^^\n Plugin: vite:vue\n File: /Users/\u003Csnip>/node_modules/@nuxt/ui/dist/runtime/components/Button.vue\n```\n\nThe result is a 500er page when visiting localhost in the web browser.\n\nI am aware there were other issues with this error message suggesting to install typescript as a devDependency. I believe this is not the solution here because typescript is already a devDependency in the ui3 starter template. Another suggestion was to add a tsconfig.json. This also already exists in the starter template.\n\nFinally, other people are experiencing the same issue, with multiple people posting the same error message in the official Nuxt Discord.\n\n### Additional context\n\nDiscord questions with the same issue\nhttps://discord.com/channels/473401852243869706/1304812159540396055\nhttps://discord.com/channels/473401852243869706/1334142349026267187\n\n\n### Logs\n\n```shell-script\n\n```",[3201,3204],{"name":3202,"color":3203},"bug","d73a4a",{"name":3190,"color":3191},3262,"ui v3 can not be started","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3262",0.75966686,{"description":3211,"labels":3212,"number":3215,"owner":3159,"repository":3159,"state":3161,"title":3216,"updated_at":3217,"url":3218,"score":3219},"Hi,\r\n\r\nI noticed that the colorscheme of the code block in the documents of modules doesn't display well in light mode.\r\n\r\nFor example, in [@nuxt/tailwindcss](https://nuxt.com/modules/tailwindcss),\r\n\r\nThe color of the code is the same as the background, for example:\r\n\r\nIn light mode, I can't see any code but comments\r\n\r\n\r\nHowever, in dark mode, it works well\r\n\r\n\r\nThe braces in the code block have a similar issue as well, \r\n\r\nIn light mode, all the braces disappear:\r\n\r\n\r\nCompared with dark mode:\r\n\r\n",[3213,3214],{"name":3170,"color":3171},{"name":3173,"color":3174},15501,"Colorscheme of code blocks in light mode seems unclear","2023-02-15T13:09:14Z","https://github.com/nuxt/nuxt/issues/15501",0.75984305,{"description":3221,"labels":3222,"number":3225,"owner":3159,"repository":3160,"state":3161,"title":3226,"updated_at":3227,"url":3228,"score":3229},"",[3223],{"name":3202,"color":3224},"ff281a",124,"Milkdown editor only works in dark mode","2023-06-06T12:14:49Z","https://github.com/nuxt/nuxt.com/issues/124",0.76205474,{"description":3231,"labels":3232,"number":3236,"owner":3159,"repository":3237,"state":3161,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nsetup fails\r\n\r\n### Additional context\r\n\r\ncc: @tobiasdiez \r\n\r\nHere are the lines\r\n\r\nhttps://github.com/nuxt/test-utils/blob/86d09da23a2d7ba6b0f3dcf2e9ca8c21655a5218/src/core/server.ts#L17-L71\r\n\r\noffending line for me was 57, but could easily be any other lines\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d\r\n\r\nis the offending commit \r\n\r\nspecifically this change\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d#diff-84e9c1e393b43cee97ce99909a2db3a09bf9a2435daa2066b01a838e206edec3\r\n\r\n### Logs\r\n\r\n```shell-script\r\nN/A\r\n```\r\n",[3233,3234],{"name":3202,"color":3203},{"name":3176,"color":3235},"5D08F5",918,"test-utils","`ctx.nuxt` does not exist when `build: false` in setup","2024-12-05T14:26:41Z","https://github.com/nuxt/test-utils/issues/918",0.7633051,{"description":3243,"labels":3244,"number":3248,"owner":3159,"repository":3160,"state":3161,"title":3249,"updated_at":3250,"url":3251,"score":3252},"Dark mode:\n- Apollo\n- Inkline\n- Lodash\n- purgecss\n- umami\n- unocss\n- xstate",[3245],{"name":3246,"color":3247},"enhancement","1ad6ff",1002,"Modules: change logos in dark mode ? ","2023-10-10T14:45:27Z","https://github.com/nuxt/nuxt.com/issues/1002",0.7634474,{"description":3254,"labels":3255,"number":3257,"owner":3159,"repository":3160,"state":3161,"title":3258,"updated_at":3259,"url":3260,"score":3261},"> As of right now, the `ui` module does not support overriding the gray color",[3256],{"name":3246,"color":3247},486,"Dark mode with custom gray palette","2022-05-18T09:03:31Z","https://github.com/nuxt/nuxt.com/issues/486",0.77010304,{"description":3263,"labels":3264,"number":3257,"owner":3159,"repository":3237,"state":3161,"title":3265,"updated_at":3266,"url":3267,"score":3261},"This way of overriding options (using spread operator):\r\nhttps://github.com/nuxt-community/module-test-utils/blob/2801ebd478d54e97d95310bbfbd69e642223f363/lib/setup.js#L13-L16\r\nis often very limiting because it makes it impossible to override particular property of an object that has other properties.\r\n\r\nFor example, if we try to override one property from object:\r\n```\r\n{\r\n i18n: {\r\n a: 1,\r\n b: 2,\r\n c: 3,\r\n }\r\n}\r\n```\r\nwith:\r\n```\r\nconst override = {\r\n i18n: {\r\n b: 4\r\n }\r\n}\r\n```\r\nthen that will override whole `i18n` object, leaving just property `b`.\r\n\r\nThis module should rather use something like this:\r\n```\r\nconst deepMerge = require('deepmerge')\r\nconst options = deepMerge.all([options, override])\r\n```\r\n(This would probably be a breaking change if one relied on previous behavior)",[],"Inflexible nuxt options override","2023-12-02T00:13:13Z","https://github.com/nuxt/test-utils/issues/486",["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEOUDDbtU1PJIOAxNfA0E9AKkp2y0IM4jhJ-w1nvVjGw":-1},"/nuxt/ui/3146"]