\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst page = ref(1)\r\nconst eventTypeFilter = reactive({\r\n options: ['a', 'b', 'c'],\r\n selected: []\r\n})\r\n\r\nconst { data, pending } = await useAsyncData(\r\n 'events',\r\n () => $fetch('/api/events', {\r\n params: {\r\n page: page.value,\r\n eventTypeFilter: eventTypeFilter.selected\r\n }\r\n }),\r\n {\r\n watch: [page, eventTypeFilter.selected]\r\n }\r\n)\r\n\u003C/script>\r\n```\r\n\r\n### Describe the bug\r\n\r\nchoosing a value does not trigger another fetch\r\n\r\n### Additional context\r\n\r\nIf I use a ref array for the model and pass that to the watcher, it works\r\n`const selectedEventTypes = ref([])`\r\n\r\n### Logs\r\n\r\n_No response_",[2051,2054],{"name":2052,"color":2053},"3.x","29bc7f",{"name":2055,"color":2056},"pending triage","E99695",27261,"Reactive object does not trigger asyncData","2024-05-17T11:17:05Z","https://github.com/nuxt/nuxt/issues/27261",0.72522575,{"description":2063,"labels":2064,"number":2070,"owner":1994,"repository":1995,"state":2009,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### Environment\n\n- Nuxt version: 3.15.1\n- Packet manager: pnpm@9.1\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nui-pro@f530918a14f2522e7126776c1d6f772ec8f8227c\n\n### Reproduction\n\nCode example on the description.\n\n### Description\n\nI’ve encountered an issue with the UDropdownMenu component where it only functions correctly when another component (in this case, a button within a UTooltip) is present. When the dropdown is used by itself (i.e., without the additional “Fisrt” button), it does not open upon interaction.\n\n**Steps to Reproduce:**\n\n1. Working Example (Dropdown works):\n\n```vue\n\u003Ctemplate>\n \u003CUTooltip>\n \u003CUButton label=\"Fisrt\" />\n \u003C/UTooltip>\n \u003CUDropdownMenu :items=\"[items, actions]\">\n \u003CUButton label=\"Second\" />\n \u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup>\nconst actions = [\n {\n label: 'Create team',\n icon: 'i-heroicons-plus-circle'\n },\n {\n label: 'Manage teams',\n icon: 'i-heroicons-cog-8-tooth'\n }\n]\n\nconst items = ref([\n {\n label: 'Profile',\n icon: 'i-lucide-user'\n },\n {\n label: 'Billing',\n icon: 'i-lucide-credit-card'\n },\n {\n label: 'Settings',\n icon: 'i-lucide-cog'\n }\n])\n\u003C/script>\n```\n\n2. Non-Working Example (Dropdown fails):\nRemove the “Fisrt” button and its wrapping UTooltip so that only the dropdown remains:\n\n\n```vue\n\u003Ctemplate>\n \u003C!-- Removed UTooltip and the first button -->\n \u003CUDropdownMenu :items=\"[items, actions]\">\n \u003CUButton label=\"Second\" />\n \u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup>\nconst actions = [\n {\n label: 'Create team',\n icon: 'i-heroicons-plus-circle'\n },\n {\n label: 'Manage teams',\n icon: 'i-heroicons-cog-8-tooth'\n }\n]\n\nconst items = ref([\n {\n label: 'Profile',\n icon: 'i-lucide-user'\n },\n {\n label: 'Billing',\n icon: 'i-lucide-credit-card'\n },\n {\n label: 'Settings',\n icon: 'i-lucide-cog'\n }\n])\n\u003C/script>\n```\n\nIn the first scenario, the dropdown opens and displays the items as expected.\n\nIn the second scenario, clicking on the button inside the UDropdownMenu does not open the dropdown.\n\nThe UDropdownMenu should work independently. Removing unrelated components (like the UTooltip with the “Fisrt” button) should not affect its functionality.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2065,2066,2069],{"name":2018,"color":2019},{"name":2067,"color":2068},"duplicate","cfd3d7",{"name":1988,"color":1989},3344,"DropdownMenu has a buggy behaviour related with other components","2025-02-19T01:59:03Z","https://github.com/nuxt/ui/issues/3344",0.726182,{"description":2076,"labels":2077,"number":2086,"owner":1994,"repository":1994,"state":2009,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25443\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst { data } = useAsyncData\u003C{ data: { test: 1 } }>(\r\n 'key',\r\n async (): Promise\u003Cany> => {\r\n return { data: { test: 1 } };\r\n },\r\n {\r\n pick: ['data'],\r\n }\r\n);\r\n\r\nconst test = computed(() => data.value?.test);\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n {{ test }}\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nTypcheck fails with `app.vue:12:41 - error TS2339: Property 'test' does not exist on type '{ data: { test: 1; }; }'.`\r\n\r\n### Describe the bug\r\n\r\nuseFetch/useAsyncData should augment the provided type via generic when pick or transform is present.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2078,2081,2082,2083],{"name":2079,"color":2080},"types","2875C3",{"name":2052,"color":2053},{"name":2018,"color":2019},{"name":2084,"color":2085},"🔨 p3-minor","FBCA04",25443,"useAsyncData/useFetch types do not reflect pick changes anymore","2024-02-12T14:42:56Z","https://github.com/nuxt/nuxt/issues/25443",0.72625023,{"description":2092,"labels":2093,"number":2096,"owner":1994,"repository":1995,"state":2009,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2094,2095],{"name":2005,"color":2006},{"name":1988,"color":1989},3525,"Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.72803265,{"description":2102,"labels":2103,"number":2104,"owner":1994,"repository":2032,"state":2009,"title":2105,"updated_at":2106,"url":2107,"score":2108},"After using `pnpm update` to upgrade vue to 3.4.3, the console throws a lot of `Hydration mismatch`. If I am using vue 3.3.13, no `Hydration mismatch` warnings will be thrown.\r\n\r\n\u003Cimg width=\"1402\" alt=\"SCR-20240103-qagg\" src=\"https://github.com/nuxt/nuxt.com/assets/133459587/188ac1c4-e19a-4570-a5d0-4863c92a7bda\">\r\n",[],1467,"About vue@3.4.3 causing hydration mismatch","2024-05-03T00:34:36Z","https://github.com/nuxt/nuxt.com/issues/1467",0.73239154,["Reactive",2110],{},["Set"],["ShallowReactive",2113],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"qhuGJP_BPEjBX8e7s6q1UBXnlbu3JNUB4yb0g8Yy12I":-1},"/nuxt/ui/3910"]