Incorrect type inference in `useAsyncData` with `transform` and `getCachedData`nuxt/nuxt · updated9 months ago · 38% similar good first issuetypes
Using `getCachedData` together with `await useLazyAsyncData` causing it to not be pending anymorenuxt/nuxt · updated8 months ago · 37% similar pending triageneeds reproduction
`useNuxtData` has data from unrelated key when using reactive keys and `useAsyncData`nuxt/nuxt · updated3 months ago · 34% similar pending triage
`useFetch` with `watch: false` and reactive key, `getCachedData` gives the old, first initialized keynuxt/nuxt · updated6 months ago · 33% similar pending triage
useAsyncData types are inferred from getCachedData and not from the handlernuxt/nuxt · closed2 years ago · 36% similar good first issuetypes3.xbug🔨 p3-minor
`getCachedData` makes `useAsyncData` resolve to type `any`nuxt/nuxt · closed2 years ago · 35% similar 3.xpending triage
useAsyncData's return type for data and error still is `| null` in v4nuxt/nuxt · closed1 year ago · 35% similar types3.xbug🔨 p3-minor
Clarify that `useAsyncData` results are not cachednuxt/nuxt · closed2 years ago · 35% similar documentationgood first issue3.x
`useAsyncData`: `getCachedData` + `immediate: false` don`t worknuxt/nuxt · closed2 years ago · 34% similar 3.xpending triage
Incorrect types in `getCachedData` when passing a `Data` type to `useFetch`nuxt/nuxt · closed2 years ago · 34% similar 3.xpending triage