` not render at server side.\n\n### Describe the bug\n\nWhen we use `useAsyncData()` and set `server: false`. the return value `pending` will get `true` at server side. It should be `false`? because this will not invoke at server side.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3150,3153],{"name":3151,"color":3152},"discussion","538de2",{"name":3135,"color":3136},15714,"`useAsyncData` return value that `pending` is `true` at server side when `server: false`","2023-02-08T02:39:02Z","https://github.com/nuxt/nuxt/issues/15714",0.6453393,{"description":3160,"labels":3161,"number":3164,"owner":3141,"repository":3141,"state":3142,"title":3165,"updated_at":3166,"url":3167,"score":3168},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.17.1`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.2`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `modules`, `css`, `app`, `experimental`, `imports`, `nitro`, `typescript`\r\n- Runtime Modules: `@pinia/nuxt@0.4.7`, `@nuxtjs/tailwindcss@6.4.1`\r\n- Build Modules: \n\n### Reproduction\n\n\r\n```\r\n// before refresh call asyncData a pending must be false\r\nconst { pending: isLoadingOne, refresh: fetchOne } = useFetch('https://jsonplaceholder.typicode.com/todos/1', { immediate: false });\r\n\r\n// before refresh call asyncData a pending must be false | perhaps a controversial case\r\nconst { pending: isLoadingTwo, refresh: fetchTwo } = await useFetch('https://jsonplaceholder.typicode.com/todos/2', { immediate: false });\r\n```\r\n\r\nSee full code: https://stackblitz.com/edit/nuxt-starter-9uxzmd?file=app.vue\n\n### Describe the bug\n\nUntil the request is forcibly invoked, it is assumed that the waiting status should be false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3162,3163],{"name":3135,"color":3136},{"name":3138,"color":3139},19218,"`useFetch/useAsyncData`: BUG: when `immediate: false`, then `pending` is `true` before call `execute/refresh` (must to be false)","2023-12-20T16:49:10Z","https://github.com/nuxt/nuxt/issues/19218",0.6517497,{"description":3170,"labels":3171,"number":3174,"owner":3141,"repository":3141,"state":3142,"title":3175,"updated_at":3176,"url":3177,"score":3178},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.6.2\r\n- Nitro Version: 2.5.2\r\n- Package Manager: pnpm@8.5.1\r\n- Builder: vite\r\n- User Config: ssr, pages, srcDir, routeRules, experimental, devtools, alias, typescript, css, app, modules, unocss, imports, components, vite\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @vueuse/nuxt@10.2.1, @unocss/nuxt@0.53.4, @vue-macros/nuxt@1.3.12, nuxt-vitest@0.8.7\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n- Github repo : https://github.com/ChronicStone/repro-issue-nuxt-useAsyncData\r\n- Live version : https://repro-issue-nuxt-use-async-data.vercel.app/\n\n### Describe the bug\n\nSince upgrating to v3.6.2, useAsyncData has inconsistent & strange behaviour.\r\nI found two main strange behaviours : \r\n\r\n### SCENARIO 1 : \r\n\r\nHere the data load once, but then the function that resolves it never runs again, no matter how the watch dependencies change.\r\n\r\nAlso, if I have the following route : `/users/profile/:userId()`\r\nWhen first visiting the page, the data will be resolved correctly if it's not already populated. If I come back to the route with a different ID, it won't re-trigger the resolver at all. I need to do a full page reload to have it resolve the correct data.\r\n\r\n### SCENARIO 2 : \r\n\r\nThe data does not load at first, and stays empty. Then, if a dependency change, it will refresh correctly.\r\n\r\n----\r\n\r\nThe reproduction provided includes the 2nd scenario, I couldn't reproduce the 1st case on a minimal setup yet. An other interesting is that on both case, devtools is completely bugged on these two cases, hitting refresh there won't do anything. You can also observe this in the provided minimal reproduction\n\n### Additional context\n\nFirst here's the context on which i'm using it\r\n- `ssr: false` in config\r\n- I'm not awaiting the useAsyncData on my component\r\n\r\nHere's an example of how i'm using it in-app : \r\n\r\n```ts\r\nconst periodFilters = ref\u003C{ month: number; year: number }>({ month: 1, year: 1 });\r\n\r\nconst { data, pending } = useAsyncData(\r\n \"assessmentCountStats\",\r\n () => StatisticsController.getAssessmentStatusCount(props.clientId, periodFilters.value),\r\n { watch: [() => props.clientId, () => periodFilters.value.year, () => periodFilters.value.month] }\r\n);\r\n```\r\n\r\nAlso worth mentionning that if I switch back to 3.6.1, everything works fine, data always update according to dependency & load correctly.\n\n### Logs\n\n_No response_",[3172,3173],{"name":3135,"color":3136},{"name":3138,"color":3139},22027,"useAsyncData has inconsistent behaviour (ssr:false) since v3.6.2","2023-07-11T07:02:52Z","https://github.com/nuxt/nuxt/issues/22027",0.6588615,{"description":3180,"labels":3181,"number":3184,"owner":3141,"repository":3141,"state":3142,"title":3185,"updated_at":3186,"url":3187,"score":3188},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.8.1\r\n- Builder: -\r\n- User Config: devtools, modules, build, typescript, supabase\r\n- Runtime Modules: @nuxtjs/supabase@1.1.3\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nUsing the following code...\r\n\r\n```vue\r\n\u003Ctemplate>\r\n {{ pending }}\r\n\r\n \u003Cinput\r\n @click=\"refresh()\"\r\n type=\"button\"\r\n value=\"Refresh\"\r\n />\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst { data, error, pending, status, refresh } = useFetch(\r\n \"https://jsonplaceholder.typicode.com/todos/1\",\r\n { immediate: false }\r\n);\r\n\u003C/script>\r\n```\r\n\r\n...you will notice that \"pending\" will remain **true** until the request is triggered at least once.\r\n\r\n### Describe the bug\r\n\r\nMaybe it is by design, but I have the feeling pending should stay **false** while not fetching, even in not immediate mode.\r\nA workaround is to use \"status === pending\" in template loaders, but I feel it less straightforward than \"pending\".\r\n\r\n### Additional context\r\n\r\nI hope my English is understandable, and thank you for your amazing work.\r\n\r\n### Logs\r\n\r\n_No response_",[3182,3183],{"name":3135,"color":3136},{"name":3138,"color":3139},23562,"useAsyncData with { immediate: false } returns pending = \"true\" until fired at least once.","2023-10-07T11:05:38Z","https://github.com/nuxt/nuxt/issues/23562",0.6630467,{"labels":3190,"number":3193,"owner":3141,"repository":3141,"state":3142,"title":3194,"updated_at":3195,"url":3196,"score":3197},[3191,3192],{"name":3135,"color":3136},{"name":3138,"color":3139},13633,"useAsyncData does not update data after first load","2023-01-19T17:02:42Z","https://github.com/nuxt/nuxt/issues/13633",0.6676409,{"labels":3199,"number":3202,"owner":3141,"repository":3141,"state":3142,"title":3203,"updated_at":3204,"url":3205,"score":3206},[3200,3201],{"name":3135,"color":3136},{"name":3138,"color":3139},14025,"useAsyncData still returning \"pending\" true when network tab shows completed","2023-01-19T17:27:45Z","https://github.com/nuxt/nuxt/issues/14025",0.67191845,{"labels":3208,"number":3213,"owner":3141,"repository":3141,"state":3142,"title":3214,"updated_at":3215,"url":3216,"score":3217},[3209,3210],{"name":3135,"color":3136},{"name":3211,"color":3212},"bug","d73a4a",12080,"useAsyncData error on dev, but ok in production","2023-01-19T15:55:10Z","https://github.com/nuxt/nuxt/issues/12080",0.671988,{"labels":3219,"number":3222,"owner":3141,"repository":3141,"state":3142,"title":3223,"updated_at":3224,"url":3225,"score":3226},[3220,3221],{"name":3135,"color":3136},{"name":3138,"color":3139},13051,"useFetch and useAsyncData can't works in event","2023-01-19T16:42:40Z","https://github.com/nuxt/nuxt/issues/13051",0.6720601,{"description":3228,"labels":3229,"number":3235,"owner":3141,"repository":3141,"state":3142,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v21.3.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: typescript, runtimeConfig, devtools, ssr, modules, features, vuetify, css, vite\r\n- Runtime Modules: vuetify-nuxt-module@0.10.3, @pinia/nuxt@0.5.1, @nuxtjs/eslint-module@4.1.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n```vue \r\n\u003Cscript lang=\"ts\" setup>\r\n// data: Ref\u003C{id: string, public: boolean}[] | null>\r\nconst { data } = useAsyncData\u003C{ id: string; public: boolean }[]>(\"/projects/\", () => $fetch(\"/projects/\"));\r\n\r\n// projects: globalThis.ComputedRef\u003C{id: string, public: boolean}[] | null>\r\nconst projects = computed(() => {\r\n // data.value: Ref\u003C{ id: string; public: boolean; }[] | null>.value: {id: string, public: boolean}[] | null\r\n return data.value;\r\n});\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003C!-- Ref returned from useAsyncData is *not* correctly resolved -->\r\n \u003Ctemplate v-for=\"project in data\" :key=\"project.id\">\r\n \u003C!-- project: project: true | {id: string, public: boolean}[] | null -->\r\n \u003C!-- Where does the true and null comes from? -->\r\n\r\n \u003C!-- Property id does not exist on type true | { id: string; public: boolean; } | []-->\r\n {{ project.id }}\r\n \u003C/template>\r\n\r\n \u003C!-- Computed property is correctly resolved -->\r\n \u003Ctemplate v-for=\"project in projects\" :key=\"project.id\">\r\n \u003C!-- project: {id: string, public: boolean -->\r\n {{ project.id }}\r\n \u003C/template>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n### Describe the bug\r\n\r\nPossibly related to #25034\r\n\r\nType of ref `data` from `useAsyncData` is correctly resolved in the script tag, but not in the template. The current workaround is adding a computed property that wraps the `data` ref. (See screenshot)\r\n\r\nThe type error is also detected by `npx nuxi typecheck` (i.e. it's not IDE bug.)\r\n\r\n\r\n\u003Cimg width=\"1456\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/6180007/635a167f-e810-4f1d-8398-d97f80732710\">\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_",[3230,3231,3232],{"name":3135,"color":3136},{"name":3138,"color":3139},{"name":3233,"color":3234},"needs reproduction","FBCA04",25698,"The data type is not resolved in the component template when using useAsyncData witch $fetch method","2024-02-13T18:17:31Z","https://github.com/nuxt/nuxt/issues/25698",0.67629975,["Reactive",3241],{},["Set"],["ShallowReactive",3244],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fthle1eEdeqesxMKe2nxQPsnVxckxouGw6kuZ2aitA9g":-1},"/nuxt/nuxt/26683"]