",[3264,3265],{"name":3177,"color":3178},{"name":3266,"color":3207},"needs reproduction",31900,"`useFetch` makes duplicate requests on client-side page navigation when wrapped in a composable","2025-04-28T05:45:41Z","https://github.com/nuxt/nuxt/issues/31900",0.6489502,{"description":3273,"labels":3274,"number":3279,"owner":3180,"repository":3180,"state":3194,"title":3280,"updated_at":3281,"url":3282,"score":3283},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.1\n- Nuxt Version: 4.1.2\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.6\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/vigorous-dewdney-859vqw?workspaceId=ws_JiUFaeQjx4GJSV6HoCZbxp\n\n### Describe the bug\n\nDescription:\nOn a fresh page load, when two useFetch calls have the same generated key and auto refresh based on the same reactive data change, one throws an error:\n\n> Error: [GET] \"/api/example?count=1\": \u003Cno response> Request aborted as another request to the same endpoint was initiated.\n\nReproduction Steps\n\n- Refresh page\n- Change reactive data point that causes the endpoints to refresh\nNotice one of the api calls throws an error\n- Change the reactive data point again\nNotice that both api calls succeed\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3275,3276],{"name":3177,"color":3178},{"name":3277,"color":3278},"possible regression","B90A42",33274,"useFetch calls with duplicate generated keys throw \"Request aborted\" error","2025-10-02T17:07:56Z","https://github.com/nuxt/nuxt/issues/33274",0.6540221,["Reactive",3285],{},["Set"],["ShallowReactive",3288],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4E3SX2BQ5wgkrHTRTmTvnxvVjAcUwyUbC5MeHEq4Ae8":-1},"/nuxt/nuxt/15528"]