\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[1995,1998],{"name":1996,"color":1997},"enhancement","a2eeef",{"name":1999,"color":2000},"triage","ffffff",3868,"ui","Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.6900893,{"description":2008,"labels":2009,"number":2013,"owner":1985,"repository":1985,"state":1987,"title":2014,"updated_at":2015,"url":2016,"score":2017},"### Describe the feature\r\n\r\nAs by default each time you update reactive data that is being used in usefetch - a fetch is called, often one may only want fetch to happen on change after a set amount of time. \r\n\r\nFor example, if you have a todo list per day and have arrows on the top to navigate between the days, you wouldn’t want the fetch to happen every time navigate happens rather only after a set amount of milliseconds which would indicate that user is not just scrolling lists rather wishes to view list/day?\r\n\r\nThoughts?\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2010],{"name":2011,"color":2012},"pending triage","E99695",26686,"[useFetch] add delay for default watch","2024-06-30T11:04:43Z","https://github.com/nuxt/nuxt/issues/26686",0.69520605,{"description":2019,"labels":2020,"number":2024,"owner":1985,"repository":2025,"state":2026,"title":2027,"updated_at":2028,"url":2029,"score":2030},"\n",[2021],{"name":2022,"color":2023},"bug","ff281a",522,"nuxt.com","closed","Checkboxes broken on dark mode","2022-05-23T15:16:45Z","https://github.com/nuxt/nuxt.com/issues/522",0.45527998,{"description":2032,"labels":2033,"number":2034,"owner":1985,"repository":1985,"state":2026,"title":2035,"updated_at":2036,"url":2037,"score":2038},"**Summary (generated)**:\n\n\"I want to request server data in real-time, and I don't want the request to be cached. I've tried adding a timestamp as the key in the request, but it didn't work. Can you help me find a solution?\"\n\n\u003Chr>\n\nAfter entering the page and completing the request, refreshing the page will not re-issue the request. My demand is to obtain the server data in real time, so I do not want to go to the cache. I have tried to add a time stamp as the key in the request, but my demand is still not met, please help me solve it, thank you very much",[],27879,"How to solve the issue where data fetched using useFetch isn't requested again after refreshing the page, you can achieve this by using React Query or by using useLayoutEffect in combination with useState and useEffect.","2024-06-28T06:07:56Z","https://github.com/nuxt/nuxt/issues/27879",0.6711207,{"description":2040,"labels":2041,"number":2044,"owner":1985,"repository":2045,"state":2026,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### 🐛 The bug\n\nUsing proxy from `useScriptClarity` to accept/decline consent doesn't work. The consent updates only after reloading the page (when using cookies/local storage instead of simple refs in useConsent file). When I tried using `window.clarity`, Clarity cookies update as expected.\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-cohqlgef?file=nuxt.config.ts\n\n### 🌈 Expected behavior\n\nCookies should update as expected.\n\n### ℹ️ Additional context\n\nInstead of viewing the preview window in StackBlitz use this link - https://nuxtstartercohqlgef-ptbs--3000--33edf5bb.local-credentialless.webcontainer.io. It seems cookies don't work in StackBlitz at all.\n\nMaybe I'm using the `useScriptClarity` composable wrong, but I'm not sure.",[2042],{"name":2022,"color":2043},"d73a4a",442,"scripts","Clarity proxy not working","2025-04-16T08:12:32Z","https://github.com/nuxt/scripts/issues/442",0.6714411,{"description":2051,"labels":2052,"number":2060,"owner":1985,"repository":1985,"state":2026,"title":2061,"updated_at":2062,"url":2063,"score":2064},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.11.0`\r\n- Nuxt Version: `3.0.0-rc.13`\r\n- Nitro Version: `0.6.1`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `runtimeConfig`, `nitro`, `modules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.1.3`, `@vueuse/nuxt@9.4.0`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nDoes not works as expected, the API call does not reflect a change in the ref. When `rfid` changes, the API call fired keeps using the old value.\r\n\r\n```\r\nconst rfid = ref(\"Value1\")\r\nrfid.value = \"Value2\"\r\n\r\nconst { data, refresh } = await useFetch\u003CIOrderPopulated[]>(\r\n `/api/orders/find?rfid=${rfid.value}`,\r\n { watch: [rfid] }\r\n)\r\n```\r\n\r\nThe same setup works with useAsynchData, the API call does reflect a change in the ref. \r\n```\r\nconst rfid = ref(\"Value1\")\r\nrfid.value = \"Value2\"\r\n\r\nconst { data, refresh } = await useAsyncData\u003CIOrderPopulated[]>(\r\n () => $fetch(`/api/orders/find?rfid=${rfid.value}`),\r\n { watch: [rfid] } \r\n)\r\n```\n\n### Describe the bug\n\nThe ref value is not updating in useFetch. The request url keeps using the same value, not reflecting the updated value from the ref. The same ref value does work when using useAsynchData. I'm not sure if I'm using useFetch in a wrong way, but since useAsynchData works fine, I'm suspecting a bug in useFetch. The problem is occurring also when not using `watch` and manually triggering the refresh.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2053,2056,2057],{"name":2054,"color":2055},"3.x","29bc7f",{"name":2011,"color":2012},{"name":2058,"color":2059},"needs reproduction","FBCA04",15359,"useFetch is not using new value from reactive object","2025-01-21T09:52:15Z","https://github.com/nuxt/nuxt/issues/15359",0.6730518,{"labels":2066,"number":2069,"owner":1985,"repository":1985,"state":2026,"title":2070,"updated_at":2071,"url":2072,"score":2073},[2067,2068],{"name":2054,"color":2055},{"name":2011,"color":2012},14292,"Respect dynamic params when calling `refresh()` returned by `useFetch`","2023-01-19T17:32:45Z","https://github.com/nuxt/nuxt/issues/14292",0.6804343,{"description":2075,"labels":2076,"number":2078,"owner":1985,"repository":1985,"state":2026,"title":2079,"updated_at":2080,"url":2081,"score":2082},"Nuxt version: 3.0.0-rc.12\r\n\r\n\r\n```ts\r\nconst activeOrder = ref(\"down\")\r\nlet {data, refresh, execute} = await useFetch\u003CPage\u003CSoftItem>>(`/api/categories/${props.cateKey}/softs`,{\r\n method: 'post',\r\n body: {\r\n orderBy: activeOrder.value,\r\n page: 1,\r\n pageSize: 5\r\n }\r\n});\r\nconst handleChangle = (value)=>{\r\n activeOrder.value = value;\r\n refresh();\r\n}\r\n```\r\nI got old result when call `handleChangle` function.\r\nHow do I refresh the request with the new parameters?",[2077],{"name":2054,"color":2055},15222,"Using useFetch, how to refresh the request with the new body content when the properties within the body change?","2023-01-19T17:46:26Z","https://github.com/nuxt/nuxt/issues/15222",0.68557143,{"description":2084,"labels":2085,"number":2088,"owner":1985,"repository":2025,"state":2026,"title":2089,"updated_at":2090,"url":2091,"score":2092},"",[2086],{"name":1996,"color":2087},"1ad6ff",611,"[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.6859272,["Reactive",2094],{},["Set"],["ShallowReactive",2097],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"OfuR1WCZb_IRYBEAFe1c-s7gnuHH3arGh5SRA4rjRQo":-1},"/nuxt/test-utils/522"]