\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n :value-key=\"undefined\"\n/>\n// will work but i need to handle label display manually using slot\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n/>\n```\n\n### Description\n\nI'm currently migrate my project to NuxtUi V3 and I have some issues with `\u003CUInputMenu />` and `\u003CUSelectMenu />`. On my selects I want to retrieve the full object selected so I don't set `value-key` but for display purpose I use the `label-key` props, however when I do this I get this typescript error on the `v-model` :\n```\nUnable to assign type 'User | undefined' to type 'string | undefined'.\nUnable to assign type 'User' to type 'string'. ts-plugin(2322)\n```\nAfter some research, I think the `label-key` alter the `value-key` type and that's what triggers the error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2014,2017,2018,2021],{"name":2015,"color":2016},"bug","d73a4a",{"name":1999,"color":2000},{"name":2019,"color":2020},"typescript","3A629E",{"name":2002,"color":2003},3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.6644056,{"description":2028,"labels":2029,"number":2032,"owner":1985,"repository":2005,"state":2006,"title":2033,"updated_at":2034,"url":2035,"score":2036},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[2030,2031],{"name":1996,"color":1997},{"name":1999,"color":2000},2948,"Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.67103314,{"description":2038,"labels":2039,"number":2040,"owner":1985,"repository":2041,"state":2006,"title":2042,"updated_at":2043,"url":2044,"score":2045},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.67491513,{"description":2047,"labels":2048,"number":2051,"owner":1985,"repository":2005,"state":2006,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI would like to keep the behavior of the popover opening only on click, but also allow it to close when something in the content slot is clicked.\n\nSuggestion:\n``` \u003CUPopover :content=\"{align: 'start'}\">\n \u003Ctemplate #default=\"{open}\">\n ....\n \u003C/template>\n \u003Ctemplate #content=\"{close}\">\n \u003Cdiv class=\"p-2\">\n \u003Cul class=\"flex flex-col gap-1 min-w-[150px]\">\n \u003Cli v-for=\"assistant in assistantsList\"\n :key=\"assistant.documentUuid\"\n @click=\"assistantSelected = assistant; close()\"\n class=\"p-1 rounded-md bg-neutral-800/40 hover:bg-neutral-800 cursor-pointer\">\n \u003Cp class=\"text-sm\">{{ assistant.name }}\u003C/p>\n \u003C/li>\n \u003C/ul>\n \u003C/div>\n \u003C/template>\n \u003C/UPopover>```\n\n### Additional context\n\n_No response_",[2049,2050],{"name":1996,"color":1997},{"name":1999,"color":2000},2789,"[v3][Popover] Close method exposed to the `content` slot","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2789",0.686015,{"description":2057,"labels":2058,"number":2066,"owner":1985,"repository":2005,"state":2006,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2059,2062,2063],{"name":2060,"color":2061},"question","d876e3",{"name":1999,"color":2000},{"name":2064,"color":2065},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.6938477,{"description":2072,"labels":2073,"number":2078,"owner":1985,"repository":2005,"state":2006,"title":2079,"updated_at":2080,"url":2081,"score":2082},"### Description\n\nIf i try to define the position of the notification using the `ui` prop `\u003CUNotifications :ui=\"{position: 'top-0 right-0'}\" />`\r\nthe \"default\" configuration is applied as well (`bottom-0 end-0 `) this happens also if defining the position using the app.config.ts.. I'm assuming i'm doing it wrong.. please advice.. \r\n",[2074,2077],{"name":2075,"color":2076},"duplicate","cfd3d7",{"name":2060,"color":2061},2180,"Notification position","2024-09-11T14:08:24Z","https://github.com/nuxt/ui/issues/2180",0.69665676,{"description":2084,"labels":2085,"number":2088,"owner":1985,"repository":2005,"state":2006,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### Environment\n\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.20.4\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.14.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.6.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\n3.0.0-alpha.4\n\n### Reproduction\n\nI don't get to seem the reproduction work in stackblitz, so here's a `setup.sh` that will demonstrate the problem.\r\n\r\n```setup.sh\r\n#!/bin/bash\r\n\r\nset -xe\r\n\r\n# Init nuxt\r\npnpm dlx nuxi@latest init --packageManager pnpm --no-gitInit nuxt-proj\r\n\r\n# Make it a workspace\r\nrm -Rf nuxt-proj/node-modules nuxt-proj/pnpm-lock.yaml\r\necho -e 'packages:\\n - \"nuxt-proj\"' > pnpm-workspace.yaml\r\n\r\n# Add @nuxt/ui next\r\ncd nuxt-proj\r\npnpm add @nuxt/ui@next\r\npnpm add -D typescript\r\npnpm install\r\n\r\n# Add @nuxt/ui module\r\ncat \u003C\u003CEOF > nuxt.config.ts\r\nexport default defineNuxtConfig({\r\n compatibilityDate: '2024-04-03',\r\n modules: [\"@nuxt/ui\"],\r\n devtools: { enabled: true }\r\n})\r\nEOF\r\n\r\n# Use nuxt ui in app.vue\r\ncat \u003C\u003CEOF > app.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUButton>Button\u003C/UButton>\r\n \u003C/div>\r\n\u003C/template>\r\nEOF\r\n\r\n# Run\r\npnpm dev\r\n```\n\n### Description\n\nWhen `@nuxt/ui` 3 is used in a pnpm workspace project, the `run dev` fails on error: \"Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type.\"\r\n\r\nWhen the workspace is removed (remove `pnpm-workspace.yaml` and run `pnpm install` in the project folder) the run works. Having `typescript` in `devDependencies` (as said in https://github.com/nuxt/ui/issues/1289#issuecomment-2345702060) does not help.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n> nuxt dev\r\n\r\nNuxt 3.13.2 with Nitro 2.9.7 \r\n \r\n ➜ Local: http://localhost:3000/\r\n ➜ Network: use --host to expose\r\n ➜ DevTools: press Shift + Alt + D in the browser (v1.5.1) \r\n\r\nℹ Nuxt Icon server bundle mode is set to local \r\n✔ Vite client built in 41ms \r\n\r\n ERROR Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type. \r\nIf this previously worked in 3.2, you can instruct the compiler to ignore this extend by adding /* @vue-ignore */ before it, for example:\r\n\r\ninterface Props extends /* @vue-ignore */ Base {}\r\n\r\nNote: both in 3.2 or with the ignore, the properties in the base type are treated as fallthrough attrs at runtime.\r\n\r\nC:/root/nuxt-proj/node_modules/.pnpm/@nuxt+ui@3.0.0-alpha.4_ioredis@5.4.1_magicast@0.3.5_postcss@8.4.47_rollup@4.23.0_vite@5.4.8_@_ytyqagzq6elb226bn7bwxmetxq/node_modules/@nuxt/ui/dist/runtime/components/Button.vue\r\n57 | const formLoading = inject\u003CRef\u003Cboolean> | undefined>(formLoadingInjectionKey, undefined)\r\n58 |\r\n59 | async function onClickWrapper(event: MouseEvent) {\r\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\r\n60 | loadingAutoState.value = true\r\n | ^^^\r\n61 | const callbacks = Array.isArray(props.onClick) ? props.onClick : [props.onClick]\r\n\r\n✔ Vite server built in 1581ms \r\n✔ Nuxt Nitro server built in 1258 ms \r\nℹ Vite client warmed up in 1ms \r\nℹ Vite server warmed up in 827ms\n```\n",[2086,2087],{"name":2015,"color":2016},{"name":1999,"color":2000},2291,"When running in pnpm workspace: \"Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type.\"","2024-10-02T12:51:09Z","https://github.com/nuxt/ui/issues/2291",0.7001566,{"description":2094,"labels":2095,"number":2098,"owner":1985,"repository":2005,"state":2006,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### Description\n\nHi 👋 and thank you for the amazing work on v3!\n\nI noticed that in v3 many component have an `as` prop that is directly bound to the `as` prop of a component from RekaUI (in many cases, `Primitive`). In NuxtUI, this prop is always typed as `any | undefined`, whereas in RekaUI the type is more constrained (a string representing a HTML tag, or a component). This can cause TypeScript, and, as a consequence, linters and IDEs, to miss some obvious errors, like if someone were to write\n\n```vue\n\u003CUInput :as=\"1\" />\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!",[2096,2097],{"name":2060,"color":2061},{"name":1999,"color":2000},3068,"[v3] `as` props typing","2025-01-10T17:28:25Z","https://github.com/nuxt/ui/issues/3068",0.70089775,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"0N2nFZdnOEKlMEiDQLLSwS_3ADvyvjh8zARMoZUlSLc":-1},"/nuxt/ui/3159"]