\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"triage","ffffff",2713,"nuxt","ui","open","UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.72367907,{"description":2880,"labels":2881,"number":2885,"owner":2872,"repository":2886,"state":2887,"title":2888,"updated_at":2889,"url":2890,"score":2891},"- [ ] Transition is missing on card hover\n",[2882],{"name":2883,"color":2884},"enhancement","1ad6ff",521,"nuxt.com","closed","[Resources] Showcases UI improvements","2022-06-14T10:45:54Z","https://github.com/nuxt/nuxt.com/issues/521",0.64557445,{"description":2893,"labels":2894,"number":2885,"owner":2872,"repository":2898,"state":2887,"title":2899,"updated_at":2900,"url":2901,"score":2891},"````\r\nimport * as _testing_library_vue from '@testing-library/vue';\r\nimport { RenderOptions as RenderOptions$1 } from '@testing-library/vue';\r\n````\r\n\r\nis being inlined in `vitest-environment-nuxt/dist/utils`, forcing the user to install `@testing-library/vue` if they use any utils provided by `vitest-environment-nuxt` even if they don't use `renderSuspended()`",[2895],{"name":2896,"color":2897},"vitest-environment","b60205","test-utils","`@testing-render/vue` is needed when using a util","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/521",{"description":2903,"labels":2904,"number":2905,"owner":2872,"repository":2886,"state":2887,"title":2906,"updated_at":2907,"url":2908,"score":2909},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nGoing to https://nuxt.com/modules/tailwindcss resulted in this:\r\n\r\n\u003Cimg width=\"573\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/26592486/c1018a94-852c-46f2-ae1b-2c42f83028e4\">\r\n\r\n**ID as Text**: `cle1::k9s6r-1697123779540-48474018b10e`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[],1368,"nuxt.com 504: GATEWAY_TIMEOUT","2023-10-18T11:04:15Z","https://github.com/nuxt/nuxt.com/issues/1368",0.71650505,{"description":2911,"labels":2912,"number":2916,"owner":2872,"repository":2872,"state":2887,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### Describe the feature\n\nApologies if the title is a bit confusing, but picture a dashboard application and a data call that depends on an optional field.\n```ts\n// some id linked to a control on the site\nconst itemId = ref\u003Cnumber>()\n\n// some data based on that id\nconst { data, status } = useFetch(() => `/api/items/${itemId.value}`)\n```\nIf `itemId` changes to a valid value, we want to leverage `useFetch` to automatically redownload this data. However, if `itemId` is null, we don't want to call `/api/items/undefined`.\n\nIn order to achieve this, we need to leverage an `AbortController` with interceptors:\n```ts\nconst controller = new AbortController()\nconst { signal } = controller\nconst { data, status } = useFetch(() => `/api/items/${itemId.value}`, {\n signal,\n onRequest () {\n if (!itemId.value) {\n controller.abort()\n }\n }\n})\n```\nOr, you basically need to manually trigger the execute/watch logic.\n\nNot sure if this would be held up by [this discussion on AbortController shortcut](https://github.com/unjs/ofetch/issues/23#issuecomment-1134481571), but I would expect it would be simple to add an optional option for a callback that is called between the `url` construction and actually executing the request.\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).",[2913],{"name":2914,"color":2915},"pending triage","E99695",31406,"Add request filter to prevent fetch from being trigger in 'invalid' states","2025-04-25T15:02:34Z","https://github.com/nuxt/nuxt/issues/31406",0.73693764,{"description":2922,"labels":2923,"number":2935,"owner":2872,"repository":2872,"state":2887,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the feature\n\nWhen loading data manually with the `useAsyncData` composables it would be useful for the refresh/execute throw an error if the refresh was cancelled/deduped and only finish the promise when the request is actually completed, it would be also useful to complete the promise and return the new data.\r\nThanks.\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).",[2924,2926,2929,2932],{"name":2883,"color":2925},"8DEF37",{"name":2927,"color":2928},"discussion","538de2",{"name":2930,"color":2931},"⚠️ breaking change","D746A6",{"name":2933,"color":2934},"4.x","3B01A5",29112,"`useAsyncData` reject promise `refresh`","2025-03-24T19:57:43Z","https://github.com/nuxt/nuxt/issues/29112",0.7375582,{"description":2941,"labels":2942,"number":2947,"owner":2872,"repository":2873,"state":2887,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.2\n- Builder: -\n- User Config: future, compatibilityDate, modules, css, experimental, runtimeConfig, routeRules, i18n, icon\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxt/image@1.9.0, @nuxtjs/i18n@9.2.0, @vueuse/nuxt@12.5.0\n- Build Modules: -\n------------------------------\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3, latest commit\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/navigation-menu\n\n### Description\n\nThe items (`\u003Cli>`) of NavigationMenu have unnecessary padding top and bottom.\n\nIs:\n\u003Cimg width=\"691\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cdb9a3e5-3429-4883-aa4a-c8e7859356f0\" />\n\nShould:\n\u003Cimg width=\"694\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/155b8a32-2e58-44b0-becf-7646c39e40f7\" />\n\nOtherwise this leads to unexpected whitespaces. E.g. the following has class `mt-0` but still shows a significant margin:\n\u003Cimg width=\"316\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/af76a978-85cd-4ed4-9269-8dfca3c9686d\" />\n\n### Additional context\n\nTabs doesnt have this:\n\u003Cimg width=\"1040\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f5849972-7c7b-421a-9f9c-03d0a73f5572\" />",[2943,2944],{"name":2866,"color":2867},{"name":2945,"color":2946},"v3","49DCB8",3328,"NavigationMenu container is too high, creates whitespace","2025-03-28T17:38:47Z","https://github.com/nuxt/ui/issues/3328",0.74179846,{"description":2953,"labels":2954,"number":2962,"owner":2872,"repository":2872,"state":2887,"title":2963,"updated_at":2964,"url":2965,"score":2966},"I'm not sure if it's a bug here. I see the timeout timer is not being cleared after the request, so it'll trigger even if the request gets a response in time. It could happen that the timeout timer of a previous request may trigger while the next request is ongoing if we call the refresh function of `useFetch`, so it may accidentally cancel the next request. \r\n\r\nhttps://github.com/nuxt/nuxt/blob/341fbe60f90a6079a391d573569ac9f32552051c/packages/nuxt/src/app/composables/fetch.ts#L151-L166",[2955,2958,2959],{"name":2956,"color":2957},"3.x","29bc7f",{"name":2866,"color":2867},{"name":2960,"color":2961},"🔨 p3-minor","FBCA04",27202,"Timeout timer invalidate in useFetch.","2024-05-22T15:00:05Z","https://github.com/nuxt/nuxt/issues/27202",0.7487348,{"description":2968,"labels":2969,"number":2972,"owner":2872,"repository":2873,"state":2887,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Environment\n\n\n Operating System: Windows_NT\n Node Version: v20.18.0\n Nuxt Version: 3.13.2\n CLI Version: 3.14.0\n Nitro Version: 2.9.7\n Package Manager: pnpm@9.12.1\n Builder: -\n User Config: -\n Runtime Modules: -\n Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nCannot use v3 on stackblitz so no repo.\n\n### Description\n\nIt looks like `onSelect?(e: Event): void` doesn't work, instead it is `select?(e: Event): void`. \nSpent a good amount of time until I figured it out. :')\nDocs problem only or something else?\n\nOnly tried nav and dropdown menus but this probably happens on all components that have onSelect:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2970,2971],{"name":2866,"color":2867},{"name":2945,"color":2946},2392,"[NavigationMenu/DropdownMenu etc] 'onSelect' doesn't work, instead it is 'select' only","2024-10-16T09:55:28Z","https://github.com/nuxt/ui/issues/2392",0.7495747,{"description":2978,"labels":2979,"number":2985,"owner":2872,"repository":2872,"state":2887,"title":2986,"updated_at":2987,"url":2988,"score":2989},"(from various references and nuxt/framework#5738 by @OhB00)\r\n\r\nWe had the ability to force refresh asyncData state using `refresh(true)`. It had been removed in nuxt/framework#699 to make refresh API forward compatible using an object syntax (`{ force: true }`) but also probably reimplement.\r\n\r\nThe main issue with refreshing while another promise is running is that we are not canceling the previous one. (and there is no standard spec for cancelable promises).\r\n\r\nFor useFetch, it is completely doable and we can use cancelation tokens to automatically cancel previous ones.\r\n\r\nFor useAsyncData as handler function that runs promise is black box, we need to find a way to reject stalled promise when it resolved and keep it in an alternative place for asyncDatas.\r\n\r\n",[2980,2981,2982],{"name":2883,"color":2925},{"name":2956,"color":2957},{"name":2983,"color":2984},"🍰 p2-nice-to-have","0E8A16",14746,"Force refresh for `useAsyncData` and `useFetch`","2023-01-19T17:39:30Z","https://github.com/nuxt/nuxt/issues/14746",0.752492,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZMVXAgYlHZea3_Y7RALBsR3f2g3lT2qS0jeLSFAb6cE":-1},"/nuxt/nuxt.com/411"]