\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[2889,2892],{"name":2890,"color":2891},"enhancement","a2eeef",{"name":2893,"color":2894},"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.7294194,{"description":2902,"labels":2903,"number":2907,"owner":2868,"repository":2868,"state":2869,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.18\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: \r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-zckkxt\r\n\r\n### Describe the bug\r\n\r\nIf you use `useFetch` with the same target url in multiple components, the application will fetch this multiple times.\r\n\r\ne.g. `useFetch('/api/random')`\r\n\r\nEven if the docs describe another behavior \r\n\r\n**From docs:**\r\n\r\nAbout Keys\r\n\r\n> [useFetch](https://nuxt.com/docs/api/composables/use-fetch) uses the provided URL as a key. Alternatively, a key value can be provided in the options object passed as a last argument.\r\n\r\nThere is a hint, about using references or functions in options\r\n\r\n> If you provide a function or ref as the url parameter, or if you provide functions as arguments to the options parameter, then the useFetch call will not match other useFetch calls elsewhere in your codebase, even if the options seem to be identical. If you wish to force a match, you may provide your own key in options.\r\n\r\nFrom Data-Fetching docs\r\n\r\n> Since the autogenerated key only takes into account the file and line where useAsyncData is invoked, it is recommended to always create your own key to avoid unwanted behavior, like when you are creating your own custom composable wrapping useAsyncData.\r\n\r\nSince `useFetch` just wraps `useAsyncData` it could be that the same rule counts for `useFetch`, but its not clear from the docs. If you read the docs you would assume that `useFetch` passes a generated key by URL to `useAsyncData` independent from the file and line where it was invoked.\r\n\r\nUsing \r\n```ts\r\nuseFetch('/api/random', { key: 'my-key' })\r\n```\r\nprevents multiple calls.\r\n\r\n\r\n### **What would be expected behaviour?**\r\nWhenever the auto-generated `key` by passed url from `useFetch` is identical across components, the composable should act same as passing the `key` as option.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2904],{"name":2905,"color":2906},"pending triage","E99695",28169,"useFetch only prevents multiple requests when `key` option is set","2024-07-16T11:21:42Z","https://github.com/nuxt/nuxt/issues/28169",0.73309284,{"description":2913,"labels":2914,"number":2917,"owner":2868,"repository":2918,"state":2919,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v21.6.1\r\n- Nuxt Version: 3.11.1\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.4\r\n- Package Manager: bun@1.0.33\r\n- Builder: -\r\n- User Config: devtools, modules, runtimeConfig, image, nitro, security\r\n- Runtime Modules: @nuxt/image@1.4.0, @nuxtjs/i18n@8.2.0, @pinia/nuxt@^0.5.1, @vueuse/nuxt@10.9.0, nuxt-security@^1.2.1, @nuxt/test-utils/module@^3.12.0\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-krtpdn-tvzxcc?file=test%2Fsomething.spec.ts\n\n### Describe the bug\n\nWithin `beforeAll()` and `afterAll()` I cant use `fetch` or `$fetch`.\r\n\r\nError in beforeAll():\r\n> Error: url is not available (is server option enabled?)\r\n\r\nError in afterAll():\r\n> Cannot set property request of FetchError: [GET] \"http://127.0.0.1:54554/api/other\": \u003Cno response> fetch failed which has only a getter\n\n### Additional context\n\nIt is crucial to test server endpoints to do some work within beforeAll and afterAll, e.g. prepare the database by creating some items and in the end cleaning everything up again.\n\n### Logs\n\n_No response_",[2915],{"name":2905,"color":2916},"5D08F5",801,"test-utils","closed","Can't fetch within beforeAll() or afterAll()","2024-03-21T18:31:27Z","https://github.com/nuxt/test-utils/issues/801",0.46656716,{"labels":2925,"number":2937,"owner":2868,"repository":2868,"state":2919,"title":2938,"updated_at":2939,"url":2940,"score":2941},[2926,2928,2931,2934],{"name":2890,"color":2927},"8DEF37",{"name":2929,"color":2930},"discussion","538de2",{"name":2932,"color":2933},"3.x","29bc7f",{"name":2935,"color":2936},"❌ 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.7070021,{"labels":2943,"number":2946,"owner":2868,"repository":2868,"state":2919,"title":2947,"updated_at":2948,"url":2949,"score":2950},[2944,2945],{"name":2932,"color":2933},{"name":2905,"color":2906},14581,"useFetch do not refetch data when use Dynamic Routes ","2023-01-19T17:37:21Z","https://github.com/nuxt/nuxt/issues/14581",0.7219456,{"description":2952,"labels":2953,"number":2964,"owner":2868,"repository":2868,"state":2919,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[Reproduction (Stackblitz)](https://stackblitz.com/edit/github-b4rxte?file=pages%2Findex.vue%3AL19)\r\n\r\n1. Start project with `npm run dev`\r\n1. Tap \"Get More\" button (data is not refreshed)\r\n1. Remove `\u003CNuxtPage />` 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_",[2954,2955,2958,2961],{"name":2905,"color":2906},{"name":2956,"color":2957},"🔨 p3-minor","FBCA04",{"name":2959,"color":2960},"suspense","C70109",{"name":2962,"color":2963},"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.7279334,{"description":2970,"labels":2971,"number":2974,"owner":2868,"repository":2975,"state":2919,"title":2976,"updated_at":2977,"url":2978,"score":2979},"\n",[2972],{"name":2878,"color":2973},"ff281a",522,"nuxt.com","Checkboxes broken on dark mode","2022-05-23T15:16:45Z","https://github.com/nuxt/nuxt.com/issues/522",0.7280715,{"description":2981,"labels":2982,"number":2974,"owner":2868,"repository":2918,"state":2919,"title":2989,"updated_at":2990,"url":2991,"score":2979},"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.",[2983,2986],{"name":2984,"color":2985},"documentation","0075ca",{"name":2987,"color":2988},"vitest-environment","b60205","Mocking multiple iterations of nuxt imports in the same test file","2024-01-24T12:25:29Z","https://github.com/nuxt/test-utils/issues/522",["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fiBE36EKYdnH1eFIdWFp3uaezkrQa826UTo1Ss4FTYFQ":-1},"/nuxt/nuxt.com/801"]