`\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",[2937,2938],{"name":2926,"color":2927},{"name":2939,"color":2940},"question","d876e3",2180,"Notification position","2024-09-11T14:08:24Z","https://github.com/nuxt/ui/issues/2180",0.7160543,{"description":2947,"labels":2948,"number":2955,"owner":2877,"repository":2878,"state":2929,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.18.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, modules\n- Runtime Modules: @nuxt/ui@3.0.1, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0\n- Build Modules: -\n- Typescript: 5.8.2\n- Vue-tsc: 2.2.8\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\n```\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n/>\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```",[2949,2950,2951,2954],{"name":2899,"color":2900},{"name":2871,"color":2872},{"name":2952,"color":2953},"typescript","3A629E",{"name":2874,"color":2875},3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.7168841,{"description":2961,"labels":2962,"number":2967,"owner":2877,"repository":2878,"state":2929,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\r\n\r\n- \"@nuxt/ui\": \"^2.18.6\",\r\n- \"nuxt\": \"^3.13.2\",\r\n- \"vue\": \"^3.5.10\",\r\n\r\n### Version\r\n\r\nv2.18.6\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n### Description\r\n\r\nHello,\r\n\r\nI'm having a important nuxt ui mono repo project and I'm encountering problems with nuxt/ui since version 6.12.0 of @nuxtjs/tailwindcss. \r\n\r\nI was forced to stay in an old version of nuxt/ui to don't have the problem : \r\n\r\n```\r\n \"pnpm\": {\r\n \"overrides\": {\r\n \"@nuxtjs/tailwindcss\": \"6.11.4\",\r\n \"@nuxt/ui\": \"2.15.2\"\r\n }\r\n },\r\n```\r\n\r\n# What happens ? \r\n\r\nAt first launch, css classes used in nuxt ui components are not correctly taken into account. \r\nIt's necessary to restart a second time the app to have the correct display\r\n\r\nThe bug is present since the version 6.12.0 of nuxtjs/tailwindcss. Maybe some effect of the First Class HMR.\r\n\r\n## Step to reproduce \r\n\r\nThe code at the following link is a minimal reproduction of my project structure : https://github.com/guirak/NuxtUiTailwindContentPurgedAtFirstLaunch\r\n\r\n- From the root project path, launch the following command : \r\n\r\n```bash\r\n# Clear the build \r\n./scripts/CleanProject.bash\r\n\r\n# Install and prepare \r\npnpm i; pnpm run dev:prepare\r\n\r\n# Launch the app\r\ncd apps/mmi-order-front-office\r\npnpm run dev\r\n```\r\n\r\n**The tailwind classes used in apps and modules are correctly displayed but the tailwind classes defined in the nuxt-ui components are not taken into account.**\r\n\r\n\r\n\r\n- Stop and restart the server\r\n\r\n```bash\r\npnpm run dev\r\n```\r\n\r\n**All tailwind classes are correctly taken into account.**\r\n\r\n\r\n\r\n\r\n\r\nThe problem is present too when building the prod version with **pnpm run build**\r\n\r\n\r\nThe problem seems to happens when using nuxt ui in a nuxt module. Please, have you any ideas, to solve this problem. \r\n\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2963,2964],{"name":2899,"color":2900},{"name":2965,"color":2966},"upstream","78bddb",2282,"Since Tailwind First Class HMR, nuxt-ui components css classes not taken into account at first launch","2024-10-18T09:16:15Z","https://github.com/nuxt/ui/issues/2282",0.7177791,{"description":2973,"labels":2974,"number":2977,"owner":2877,"repository":2878,"state":2929,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### 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_",[2975,2976],{"name":2868,"color":2869},{"name":2871,"color":2872},2789,"[v3][Popover] Close method exposed to the `content` slot","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2789",0.72072756,{"description":2983,"labels":2984,"number":2987,"owner":2877,"repository":2878,"state":2929,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### 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!",[2985,2986],{"name":2939,"color":2940},{"name":2871,"color":2872},3068,"[v3] `as` props typing","2025-01-10T17:28:25Z","https://github.com/nuxt/ui/issues/3068",0.7247434,["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ffTDzbmnw-F2pPWjeLZgqGhqIvEw4o5M6KQIOoQ5VDaA":-1},"/nuxt/ui/2291"]