` from `pages/index.vue` and save.\r\n1. Fully reload the browser preview.\r\n1. Tap \"Get More\" (data is refreshed)\n\n### Describe the bug\n\nWhen a nested route is given with `\u003CNuxtPage />`, the refresh option of `useAsyncData` and `useFetch` fails. \r\n\r\nThis issue appears in Nuxt 3.6.4–3.7.0. The last working version was 3.6.3.\r\n\r\nThis appears to be regardless of what's contained in nested route or whether nested route is the currently active route.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[1998,1999,2002],{"name":1985,"color":1986},{"name":2000,"color":2001},"🔨 p3-minor","FBCA04",{"name":2003,"color":2004},"suspense","C70109",22955,"Refresh of useFetch/useAsyncData broken when nested route is present","2024-11-19T16:20:55Z","https://github.com/nuxt/nuxt/issues/22955",0.7397364,{"description":2011,"labels":2012,"number":2016,"owner":1988,"repository":2017,"state":2018,"title":2019,"updated_at":2020,"url":2021,"score":2022},"I would like us to explore the usage of the hybrid rendering of Nuxt to improve the speed of dev.nuxt.com.\n\nBasically, we need to pre-render all the pages and leverage the SWR on:\n- `/modules`\n- `/modules/:slug` (coming in #673 )\n- `/resources/showcases`\n- `/community/repositories`\n- `/community/nuxters`\n- `/community/jobs` (coming in #770)\n\nThese pages leverage query params, ex: `/community/nuxters?time=week`\n\n@pi0 can we setup a call with @benjamincanac and myself to see the best way to implement this? Or guiding us on how to configure Nuxt to support this?",[2013],{"name":2014,"color":2015},"enhancement","1ad6ff",801,"nuxt.com","closed","[Performance] Leverage Hybrid Rendering","2022-10-28T14:39:31Z","https://github.com/nuxt/nuxt.com/issues/801",0.47167528,{"labels":2024,"number":2031,"owner":1988,"repository":1988,"state":2018,"title":2032,"updated_at":2033,"url":2034,"score":2035},[2025,2028],{"name":2026,"color":2027},"3.x","29bc7f",{"name":2029,"color":2030},"pending triage","E99695",14233,"useAsyncData refresh unexpectedly when using Route Params values in the fetch url","2023-01-19T17:30:49Z","https://github.com/nuxt/nuxt/issues/14233",0.71454674,{"labels":2037,"number":2047,"owner":1988,"repository":1988,"state":2018,"title":2048,"updated_at":2049,"url":2050,"score":2051},[2038,2040,2043,2044],{"name":2014,"color":2039},"8DEF37",{"name":2041,"color":2042},"discussion","538de2",{"name":2026,"color":2027},{"name":2045,"color":2046},"❌ won't do","705B27",14583,"support computed keys for data fetching composables","2023-03-13T10:11:38Z","https://github.com/nuxt/nuxt/issues/14583",0.71506965,{"labels":2053,"number":2056,"owner":1988,"repository":1988,"state":2018,"title":2057,"updated_at":2058,"url":2059,"score":2060},[2054,2055],{"name":2026,"color":2027},{"name":2029,"color":2030},14292,"Respect dynamic params when calling `refresh()` returned by `useFetch`","2023-01-19T17:32:45Z","https://github.com/nuxt/nuxt/issues/14292",0.7253617,{"labels":2062,"number":2065,"owner":1988,"repository":1988,"state":2018,"title":2066,"updated_at":2067,"url":2068,"score":2069},[2063,2064],{"name":2026,"color":2027},{"name":2029,"color":2030},14581,"useFetch do not refetch data when use Dynamic Routes ","2023-01-19T17:37:21Z","https://github.com/nuxt/nuxt/issues/14581",0.72679913,{"description":2071,"labels":2072,"number":2075,"owner":1988,"repository":2017,"state":2018,"title":2076,"updated_at":2077,"url":2078,"score":2079},"\n",[2073],{"name":1985,"color":2074},"ff281a",522,"Checkboxes broken on dark mode","2022-05-23T15:16:45Z","https://github.com/nuxt/nuxt.com/issues/522",0.73060745,{"description":2081,"labels":2082,"number":2075,"owner":1988,"repository":2089,"state":2018,"title":2090,"updated_at":2091,"url":2092,"score":2079},"Hey I was using `mockNuxtImport` to mock 2 different users from a nuxt composable in the same test file. It seems to use the last `mockNuxtImport` that is called in the file, not the one scoped to the test.\r\n\r\n```ts\r\nit('renders the users email', () => {\r\n\tmockNuxtImport('useSupabaseUser', () => {\r\n\t\treturn () => mockUser\r\n\t})\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('jdoe@gmail.com')).toBeInTheDocument()\r\n})\r\n\r\nit('renders the Error when there is no user', () => {\r\n\tmockNuxtImport('useSupabaseUser', () => {\r\n\t\treturn () => {}\r\n\t})\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('Error')).toBeInTheDocument()\r\n})\r\n```\r\n\r\nThe first test fails here as it thinks `useSupabaseUser` returns {}\r\n\r\nI did manage to get this working with a global variable:\r\n\r\n```ts\r\nlet mockUser = { id: 1, name: 'John Doe', email: 'jdoe@gmail.com' }\r\n\r\nmockNuxtImport('useSupabaseUser', () => {\r\n\treturn () => mockUser\r\n})\r\n\r\nit('renders the users email', () => {\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('jdoe@gmail.com')).toBeInTheDocument()\r\n})\r\n\r\nit('renders the Error when there is no user', () => {\r\n\tmockUser = {}\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('Error')).toBeInTheDocument()\r\n})\r\n```\r\n\r\nNot really sure if this is expected, it seems a little strange to me, so figured I post my findings.",[2083,2086],{"name":2084,"color":2085},"documentation","0075ca",{"name":2087,"color":2088},"vitest-environment","b60205","test-utils","Mocking multiple iterations of nuxt imports in the same test file","2024-01-24T12:25:29Z","https://github.com/nuxt/test-utils/issues/522",{"description":2094,"labels":2095,"number":2097,"owner":1988,"repository":1988,"state":2018,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.2\r\n- CLI Version: 3.10.1\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\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ftrxnd?file=pages%2Ffetch.vue\r\n\r\n### Describe the bug\r\n\r\nWhile playing around using `useRouteQuery` composable fromVueUse library, I have noticed different behaviour watching the `ref` retrieved from `useRouteQuery` when using it with `useFetch` vs `useAsyncData`.\r\nWhenever `useAsyncData` is used to call the API and `ref` from `useRouteQuery` is listed inside `watch` array, API is being called only once whenever ref value changes. As expected.\r\nBut it is different with `useFetch`, where whenever `ref` value updates, there are two API calls made where one is cancelled by dedupe.\r\n\r\nI have prepared reproduction with two different pages, each for different implementation where behaviour can be observed.\r\nI would assume it has to do with `ref` being updated twice because URL query sync, but I am not sure why it differs.\r\n\r\nAlso I am aware of https://github.com/nuxt/nuxt/issues/24788 but trying to use vueuse implementation as of now.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2096],{"name":2029,"color":2030},25852,"`useAsyncData` watch vs `useFetch` watch with `useRouteQuery` ref","2025-04-02T12:46:45Z","https://github.com/nuxt/nuxt/issues/25852",0.732434,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"vKB0jLUs01AHR42fN3gV5RWx9IjNma5P8CHPVcHonss":-1},"/nuxt/test-utils/801"]