Incorrect type inference in `useAsyncData` with `transform` and `getCachedData`nuxt/nuxt · updated1 year ago · 38% similar good first issuetypes
`useFetch` with `watch: false` and reactive key, `getCachedData` gives the old, first initialized keynuxt/nuxt · updated9 months ago · 36% similar pending triage
When two useAsyncData with same key refresh at same time, only one of them updates.nuxt/nuxt · closed3 years ago · 39% similar 3.xpending triage
Clarify that `useAsyncData` results are not cachednuxt/nuxt · closed2 years ago · 37% similar documentationgood first issue3.x
[BUG]: Issue with documentation for useAsyncData (`getCachedData` method)nuxt/nuxt · closed20 days ago · 37% similar pending triage
`useFetch/useAsyncData`: BUG: when `immediate: false`, then `pending` is `true` before call `execute/refresh` (must to be false)nuxt/nuxt · closed2 years ago · 36% similar 3.xpending triage
calling `useNuxtData` before a fetch composable causes shared key cache to purge on navigation for nuxt `3.17.x`nuxt/nuxt · closed9 months ago · 35% similar ❗ p4-importantpossible regression
useAsyncData use $csrfFetchnuxt/nuxt · closed1 year ago · 35% similar pending triageneeds reproduction
useAsyncData types are inferred from getCachedData and not from the handlernuxt/nuxt · closed2 years ago · 35% similar good first issuetypes3.xbug🔨 p3-minor
Vite treats the logic in useAsyncData() as client logicnuxt/nuxt · closed7 months ago · 35% similar pending triage