\n \u003C/NuxtLayout>\n \u003C/UApp>\n\u003C/template>\n\u003Cscript setup lang=\"ts\">\nimport {TooltipProviderProps} from \"reka-ui\";\n\nconst tooltipProps : TooltipProviderProps = {\n delayDuration: 700,\n skipDelayDuration: 300,\n disableHoverableContent: false,\n disableClosingTrigger: false,\n disabled: false,\n ignoreNonKeyboardFocus: false,\n}\n\u003C/script>\n```\n**nuxt.config.ts**\n```\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: '2024-11-01',\n ssr: false,\n srcDir: 'src',\n devtools: { enabled: true },\n modules: [\n '@nuxt/ui',\n '@pinia/nuxt',\n '@nuxt/image',\n 'nuxt-icons',\n '@nuxtjs/i18n',\n ],\n css: ['~/assets/css/main.css']\n})\n```\nI found that when Nuxt3 SSR is set to false, the tooltip and toast do not display, and the tooltip also reports an error of 500\n\nInjection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n\nI hope to find a solution.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3060,3063,3066,3067],{"name":3061,"color":3062},"bug","d73a4a",{"name":3064,"color":3065},"needs reproduction","CB47CF",{"name":3024,"color":3025},{"name":3068,"color":3069},"triage","ffffff",3932,"Nuxt3 SSR is set to false, the tooltip and toast become invalid","2025-04-30T13:24:47Z","https://github.com/nuxt/ui/issues/3932",0.7648413,{"labels":3076,"number":3087,"owner":3027,"repository":3027,"state":3029,"title":3088,"updated_at":3089,"url":3090,"score":3091},[3077,3080,3083,3084],{"name":3078,"color":3079},"enhancement","8DEF37",{"name":3081,"color":3082},"discussion","538de2",{"name":3047,"color":3048},{"name":3085,"color":3086},"🍰 p2-nice-to-have","0E8A16",14329,"Config alias `theme` to `extends`","2023-01-19T17:33:54Z","https://github.com/nuxt/nuxt/issues/14329",0.7665432,{"description":3093,"labels":3094,"number":3097,"owner":3027,"repository":3027,"state":3029,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Environment\r\n\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.12.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: `modules`, `i18n`, `image`, `content`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.2.0`, `@pinia/nuxt@0.4.6`, `@nuxtjs/i18n@8.0.0-beta.7`, `@nuxt/image-edge@1.0.0-27840416.dc1ed65`, `@nuxt/content@2.3.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n1. Create ```app.config.ts``` File. Following code is example in my project.\r\n```\r\nexport default defineAppConfig({\r\n blogTags: [\r\n 'Node Js',\r\n 'Get Started',\r\n 'Typescript',\r\n 'Gatsby',\r\n 'JavaScript',\r\n 'Next',\r\n 'Nuxt',\r\n 'MDX'\r\n ]\r\n})\r\n```\r\n\r\n2. Call ```useAppConfig()```. ```const appConfig = useAppConfig()```\r\n3. Create any plugins\r\n\r\n### Describe the bug\r\n\r\nThere is a bug when I call ```useAppConfig()``` with plugins\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3095,3096],{"name":3047,"color":3048},{"name":3050,"color":3051},12545,"Uncaught ReferenceError: defineAppConfig is not defined at defu.mjs:45:2","2023-02-10T11:19:05Z","https://github.com/nuxt/nuxt/issues/12545",0.76949656,{"description":3103,"labels":3104,"number":3108,"owner":3027,"repository":3028,"state":3029,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x / v3.x\n\n### Description\n\nMaybe this is just not documented:\n\n`SelectMenu` has a [creatable](https://ui.nuxt.com/components/select-menu#creatable) prop. In most use cases the created item needs to be save to the database. According to the docs there seems to be no option to do so. E.g. I want to make a database request or even open a modal for advanced item creation.\n\n### Additional context\n\n_No response_",[3105,3107],{"name":3078,"color":3106},"a2eeef",{"name":3024,"color":3025},2739,"SelectMenu: Use \"creatable\" with async function (e.g. save created item into database)","2024-12-06T14:14:20Z","https://github.com/nuxt/ui/issues/2739",0.7704365,{"description":3114,"labels":3115,"number":3119,"owner":3027,"repository":3028,"state":3029,"title":3120,"updated_at":3121,"url":3122,"score":3123},"> You can change the `content` width globally using your `app.config.ts`:\n> \n> ```ts\n> export default defineAppConfig({\n> ui: {\n> select: {\n> slots: {\n> content: 'min-w-fit'\n> }\n> }\n> }\n> })\n> ``` \n\n _Originally posted by @benjamincanac in [#4300](https://github.com/nuxt/ui/issues/4300#issuecomment-2961842289)_\n\n\nplease,\ndocument in its page:\nhttps://ui.nuxt.com/components/select\n\nalso, consider to add access to \"content\" through \"ui\" prop to make it, not only globally, but particularly available.\nNow you can't do: \n```html\n\u003CUSelect :ui=\"{ content: 'min-w-fit' }\" ... />\n```\n\nI had to search hard to find my own answer, and I think it's a very important case for everyone. It will benefit us all.\nThank you in advance!",[3116],{"name":3117,"color":3118},"documentation","0075ca",4409,"USelect > document how to make items/options content width, fit the longest item/option width. Add an image example.","2025-07-08T10:43:50Z","https://github.com/nuxt/ui/issues/4409",0.7797401,{"description":3125,"labels":3126,"number":3129,"owner":3027,"repository":3028,"state":3029,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Description\n\nHi guys would be nice if there's a config value that sets `progress: false`, cause someone doesn't like it...\nit can be disabled on ui with display none, but a more correct approach would be in app config.\nThanks.\n\n### Additional context\n\n\u003Cimg width=\"382\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fc3885e7-fcfb-4950-a239-f0e4053de69d\" />",[3127,3128],{"name":3078,"color":3106},{"name":3024,"color":3025},3270,"[Feature request] Toast hide progress in app.config","2025-05-12T12:47:03Z","https://github.com/nuxt/ui/issues/3270",0.7840173,{"description":3135,"labels":3136,"number":3143,"owner":3027,"repository":3028,"state":3029,"title":3144,"updated_at":3145,"url":3146,"score":3147},"### Description\n\nHello!\r\n\r\nI think it would be nice to allow multiple notifications containers, so that we could have different placements for toasts based on the container they are sent to.\r\n\r\nAfter digging in the components i think this changes wouldn't be heavy and i could contribute for this if you agree with this feature request.\r\n\r\nMy idea would be to allow to pass a custom key for the the useToast and the notifications state and therefore they would have their own references:\r\n```\r\nNotifications.vue\r\nconst toast = useToast(aCustomKey)\r\nconst notifications = useState\u003CNotification[]>(aCustomKey, () => [])\r\n```\r\n\r\n----\r\n\r\nSo now we could have:\r\n```\r\nApp.vue\r\n\u003CUNotifications :ui=\"{position:'bottom-auto top-0' }\"/>\r\n\u003CUNotifications state-key=\"aCustomKey\" :ui=\"{position:'bottom-0 top-auto' }\"/>\r\n```\r\n\r\nAnd then within your app we could call the toast handler we want:\r\n```\r\nRandom.vue\r\nconst toast = useToast(aCustomKey)\r\n```\r\n\r\nLet me know what you think and if you'll be interested on this knowing that i could contribute fully to it.\r\n\r\nThanks!\n\n### Additional context\n\n_No response_",[3137,3138,3141],{"name":3078,"color":3106},{"name":3139,"color":3140},"closed-by-bot","ededed",{"name":3142,"color":3140},"stale",1706,"Allow multiple notifications containers","2025-06-19T02:12:39Z","https://github.com/nuxt/ui/issues/1706",0.78411597,["Reactive",3149],{},["Set"],["ShallowReactive",3152],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fCIwsWrBgGOuKghXybSbU3zCfI9LwGlyjFNsrBuXL5Tw":-1},"/nuxt/ui/4153"]