Custom `useFetch` has incorrect type for `default` optionnuxt/nuxt · updated5 months ago · 35% similar documentationtypes🍰 p2-nice-to-have
"UseFetchType" and also transforms the result into the desired output format using another transformer.nuxt/nuxt · updated10 months ago · 35% similar pending triage
type of `default` option in `useFetch` is not correctnuxt/nuxt · closed13 months ago · 42% similar types3.x🔨 p3-minor
`useFetch()` incorrectly typed errornuxt/nuxt · closed27 months ago · 42% similar types3.xbug🍰 p2-nice-to-have
`useFetch` returns the `.data` property as `any`nuxt/nuxt · closed27 months ago · 40% similar 3.xpending triage
`compatibilityVersion 4` doesn't change `useFetch` return data typesnuxt/nuxt · closed4 months ago · 38% similar typespending triagepossible regression
`asyncData` and `useFetch` return types are currently broken with optionsnuxt/nuxt · closed27 months ago · 37% similar 3.xbug
useFetch and useLazyFetch export incorrect typescript type from apinuxt/nuxt · closed27 months ago · 37% similar 3.xpending triageneeds reproduction
TypeScript type error in `useFetch` default option with `ResT` generic and `transform` returning `unknown` when making external server requestsnuxt/nuxt · closed21 months ago · 37% similar types3.xpending triage
Type issue when using `useFetch` with baseURLnuxt/nuxt · closed16 months ago · 36% similar 3.xpending triage