` 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_",[3218,3219,3222,3225],{"name":3160,"color":3161},{"name":3220,"color":3221},"🔨 p3-minor","FBCA04",{"name":3223,"color":3224},"suspense","C70109",{"name":3226,"color":3227},"possible regression","B90A42",22955,"Refresh of useFetch/useAsyncData broken when nested route is present","2025-05-29T21:22:14Z","https://github.com/nuxt/nuxt/issues/22955",0.72793335,{"description":3234,"labels":3235,"number":3238,"owner":3149,"repository":3174,"state":3175,"title":3239,"updated_at":3240,"url":3241,"score":3242},"\n",[3236],{"name":3146,"color":3237},"ff281a",522,"Checkboxes broken on dark mode","2022-05-23T15:16:45Z","https://github.com/nuxt/nuxt.com/issues/522",0.7280715,{"description":3244,"labels":3245,"number":3238,"owner":3149,"repository":3252,"state":3175,"title":3253,"updated_at":3254,"url":3255,"score":3242},"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.",[3246,3249],{"name":3247,"color":3248},"documentation","0075ca",{"name":3250,"color":3251},"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":3257,"labels":3258,"number":3261,"owner":3149,"repository":3149,"state":3175,"title":3262,"updated_at":3263,"url":3264,"score":3265},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v19.5.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `modules`, `runtimeConfig`, `content`, `image`, `googleFonts`\r\n- Runtime Modules: `@nuxt/content@2.5.2`, `@nuxtjs/google-fonts@3.0.0`, `@nuxt/image-edge@1.0.0-27968280.9739e4d`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe following code fetches search results. It's automatically refreshed when the searchquery ref is changed.\r\n\r\n```javascript\r\nconst navSearchAPICall = useLazyAsyncData(\r\n 'searchWorking',\r\n () => $fetch('/api/search', {\r\n params: {\r\n query: searchquery.value\r\n }\r\n }),\r\n { \r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\nThis works as expected. But the following code, wich should behave the same according to the documentation, does not work. The request is refreshed when the searchquery ref changes, but the query parameters stay the same.\r\n\r\n```javascript\r\nconst searchAPICall = useLazyFetch('/api/search', {\r\n key: 'searchNotWorking',\r\n params: {\r\n query: searchquery.value\r\n },\r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\n\r\n\n\n### Describe the bug\n\nAs described in the reproduction, when using `useLazyAsyncData`, the request is refreshed with updated query parameters according to the searchquery ref. \r\n\r\nBut when using `useLazyFetch`, the request is refreshed but sent with unchanged query parameters.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3259,3260],{"name":3188,"color":3189},{"name":3160,"color":3161},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.73139465,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fvKB0jLUs01AHR42fN3gV5RWx9IjNma5P8CHPVcHonss":-1},"/nuxt/test-utils/801"]