\n```",[1984,1987],{"name":1985,"color":1986},"question","d876e3",{"name":1988,"color":1989},"v3","49DCB8",3517,"nuxt","ui","open","How To Style NavigationMenu items","2025-03-14T13:01:49Z","https://github.com/nuxt/ui/issues/3517",0.70333683,{"description":1999,"labels":2000,"number":2003,"owner":1991,"repository":1992,"state":1993,"title":2004,"updated_at":2005,"url":2006,"score":2007},"### Description\n\nHi there,\n\nI'm really curious about how Nuxt UI is handling trailing slashes. In the Nuxt Content repo I can see they are using `ufo` to remove the trailing slashes, but in the Nuxt UI repo I can't find how you get rid of it. Even tho I know you can do these things on Vercel and Netlify, I'm curious how you handle it in Nuxt UI.\n\nIn my case, route.path is returning a path with a trailing slash and breaks my `queryCollection`...\n\n```vue\nconst { data: page } = await useAsyncData(\n `${route.path}/.navigation`,\n async () => {\n return await queryCollection('content').path(route.path).first();\n }\n);\n```",[2001,2002],{"name":1985,"color":1986},{"name":1988,"color":1989},3285,"Trailing slashes","2025-02-10T13:25:12Z","https://github.com/nuxt/ui/issues/3285",0.7127764,{"description":2009,"labels":2010,"number":2011,"owner":1991,"repository":2012,"state":1993,"title":2013,"updated_at":2014,"url":2015,"score":2016},"### Describe the feature\n\nI found, how to deploy nuxt 2 app into gcp app engine. But there is no doc about nuxt 3\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] 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).",[],1764,"nuxt.com","deploy nuxt 3 on gcp appengine","2025-01-22T09:58:41Z","https://github.com/nuxt/nuxt.com/issues/1764",0.71510315,{"description":2018,"labels":2019,"number":2023,"owner":1991,"repository":1992,"state":2024,"title":2025,"updated_at":2026,"url":2027,"score":2028},"### Environment\n\nNuxt project info: 12:26:48 PM\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.16.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.9.0\r\n- Builder: -\r\n- User Config: devtools, ssr, typescript, imports, modules, svgo, mongoose, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/test-utils/module@3.14.1, nuxt-mongoose@1.0.6, @pinia/nuxt@0.5.4, @nuxt/ui@2.18.4, @nuxtjs/i18n@8.5.2, nuxt-svgo@4.0.5\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nthe online address: https://nano-portfolio-ruby.vercel.app/\r\nthe repo: https://github.com/gaomingzhao666/nano-portfolio\n\n### Description\n\nHey, I don't install `nuxt-icon` module and I can use icons directly in `nuxt-ui`, because I think the `nuxt-ui` already integrated `nuxt-icon` module.\r\n\r\nThe problem is: that the icon is empty when users first enter the page that shows icons, and when I turn off the computer and open it in next day, the bug is reproduced.\r\n\r\nI think the server cache is not working properly, should I install `nuxt-icon` module manually or it's just a bug to `nuxt-ui`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2020],{"name":2021,"color":2022},"bug","d73a4a",2195,"closed","the `icon` component that integrated in `nuxt-ui` by default is not shown at first loading","2024-09-27T04:02:26Z","https://github.com/nuxt/ui/issues/2195",0.6557746,{"description":2030,"labels":2031,"number":2037,"owner":1991,"repository":1992,"state":2024,"title":2038,"updated_at":2039,"url":2040,"score":2041},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2032,2033,2034],{"name":2021,"color":2022},{"name":1988,"color":1989},{"name":2035,"color":2036},"triage","ffffff",3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.70313776,{"description":2043,"labels":2044,"number":2047,"owner":1991,"repository":1992,"state":2024,"title":2048,"updated_at":2049,"url":2050,"score":2051},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.3.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.18.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.1\n\n### Reproduction\n\nhttps://github.com/fl5brkv/nuxt-issue\n\n### Description\n\nI installed nuxt ui 3 from the official nuxt ui starter, just wanted to try the calendar, but it doesnt work. Throwing me warnings in console.log.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Failed to resolve component: UCalendar\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n\nruntime-core.esm-bundler.js?v=b66559bc:50 [Vue warn]: Hydration node mismatch:\n- rendered on server: \u003C!----> \n- expected on client: UCalendar \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```",[2045,2046],{"name":2021,"color":2022},{"name":1988,"color":1989},3044,"\u003CUCalendar /> isn't rendering","2025-01-08T09:24:13Z","https://github.com/nuxt/ui/issues/3044",0.70378286,{"description":2053,"labels":2054,"number":2057,"owner":1991,"repository":1992,"state":2024,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.16.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.1\n- Builder: -\n- User Config: devtools, compatibilityDate, modules, app, css, colorMode, svgSprite, future, imports, runtimeConfig, ssr\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.13, @nuxt/eslint@1.1.0, @nuxt/icon@1.10.3, @nuxtjs/svg-sprite@1.0.2, @nuxt/image@1.9.0, @vueuse/nuxt@12.7.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\n### Description\n\n### Help Nuxt ui 3 table not reactive\n\nWhen I click the button, the table doesn't update. However, when I print the array object, the data is added, but the table still does not update\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\nThank you for help\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2055,2056],{"name":2021,"color":2022},{"name":1988,"color":1989},3377,"UI Table is not reactive","2025-02-27T21:19:42Z","https://github.com/nuxt/ui/issues/3377",0.705227,{"description":2063,"labels":2064,"number":2070,"owner":1991,"repository":1992,"state":2024,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.20.5\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-vuefire@1.0.4, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n\n\n\n\n```\n \u003CUTooltip :delay-duration=\"0\" :text=\"`R$ ${transactionCost.brl}`\">\n \u003CUIcon class=\"text-yellow-500 text-xs\" name=\"i-lucide-coins\" />\n \u003Cp class=\"text-neutral-200 text-xs\">\n {{ transactionCost.credits }}\n \u003C/p>\n\u003C/UTooltip>\n```\n\n``` \n\u003CNuxtLayout>\n \u003CUApp :toaster=\"{ position: 'top-right' }\">\n \u003CNuxtPage />\n \u003C/UApp>\n\u003C/NuxtLayout>\n```\n\n\n### Description\n\nThe `app.vue` is already using the `UApp`. When I try to add a `UTooltip` inside the modal, it throw an error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```\nUncaught (in promise) Error: Injection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n```",[2065,2066,2069],{"name":2021,"color":2022},{"name":2067,"color":2068},"needs reproduction","CB47CF",{"name":1988,"color":1989},2801,"[v3][UTooltip] `UTooltip` inside `UModal` causing error","2025-02-06T15:28:30Z","https://github.com/nuxt/ui/issues/2801",0.7097036,{"description":2076,"labels":2077,"number":2080,"owner":1991,"repository":1992,"state":2024,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.38\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, @nuxtjs/i18n@9.1.0, @nuxt/image@1.8.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\nUse the UPopover component and put a UButton in an UTooltip.\n\n### Description\n\nUPopover does not work when the UButton is in a UTooltip\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2078,2079],{"name":2021,"color":2022},{"name":1988,"color":1989},2897,"UPopover does not work when the UButton is in a UTooltip","2025-02-19T15:23:15Z","https://github.com/nuxt/ui/issues/2897",0.7101173,{"description":2086,"labels":2087,"number":2090,"owner":1991,"repository":1992,"state":2024,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Description\n\nHi,\n\nhere in the first form in nuxtui2\nhttps://ui.nuxt.com/components/form \nthe behaviour is that the input field is validated after the blur. If there is an error and I correct it, the error is fixed immediately.\n\nIn v3 the behaviour is different. I have seen the prop validateOn so I can change it to blur, but not like first onBlur and then onInput like in v2.\n\nbest,\ngregor",[2088,2089],{"name":2021,"color":2022},{"name":1988,"color":1989},3006,"How can I get the same form validation behaviour as in v2?","2025-01-06T17:48:11Z","https://github.com/nuxt/ui/issues/3006",0.7108159,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"FLytn0xS0NXXHIZK5MS4KTfUMDCqri_EHEK2p5MAh0I":-1},"/nuxt/ui/2931"]