Incorrect type inference in `useAsyncData` with `transform` and `getCachedData`nuxt/nuxt · updated10 months ago · 38% similar good first issuetypes
only null Type is allowed to useAsyncData's default Typenuxt/nuxt · closed2 years ago · 41% similar types3.xpending triageneeds reproduction
`compatibilityVersion 4` doesn't change `useFetch` return data typesnuxt/nuxt · closed12 months ago · 40% similar typespending triagepossible regression
useAsyncData types are inferred from getCachedData and not from the handlernuxt/nuxt · closed2 years ago · 39% similar good first issuetypes3.xbug🔨 p3-minor
type issue when returning undefined with `getCachedData`nuxt/nuxt · closed1 year ago · 39% similar typesbug🔨 p3-minor
`useFetch` returns the `.data` property as `any`nuxt/nuxt · closed3 years ago · 39% similar 3.xpending triage
Setting `experimental.defaults.useAsyncData.value` does not update TS typesnuxt/nuxt · closed6 months ago · 39% similar good first issuetypes3.x
Type issue with the value ref of useAsyncDatanuxt/nuxt · closed2 years ago · 38% similar 3.xpending triage
Types improvement to `asyncData` with the `default` optionnuxt/nuxt · closed3 years ago · 38% similar types3.xdx🍰 p2-nice-to-have
[Typescript] useAsyncData looses the type of response, when pick option is not specified for certain typesnuxt/nuxt · closed3 years ago · 38% similar types3.x🔨 p3-minor