Similar issues - #14437 - nuxt/nuxt - unsight.dev

# Custom `useFetch` has incorrect type for `default` option

Custom `useFetch` has incorrect type for `default` option

nuxt/nuxt · updated6 months ago · 36% similar

documentationtypes🍰 p2-nice-to-have

"UseFetchType" and also transforms the result into the desired output format using another transformer.

nuxt/nuxt · updated11 months ago · 35% similar

pending triage

type of `default` option in `useFetch` is not correct

nuxt/nuxt · closed15 months ago · 42% similar

types3.x🔨 p3-minor

`useFetch()` incorrectly typed error

nuxt/nuxt · closed29 months ago · 42% similar

types3.xbug🍰 p2-nice-to-have

`useFetch` returns the `.data` property as `any`

nuxt/nuxt · closed29 months ago · 40% similar

3.xpending triage

TypeScript type error in `useFetch` default option with `ResT` generic and `transform` returning `unknown` when making external server requests

nuxt/nuxt · closed23 months ago · 39% similar

types3.xpending triage

`asyncData` and `useFetch` return types are currently broken with options

nuxt/nuxt · closed29 months ago · 38% similar

3.xbug

`compatibilityVersion 4` doesn't change `useFetch` return data types

nuxt/nuxt · closed5 months ago · 38% similar

typespending triagepossible regression

Type issue when using `useFetch` with baseURL

nuxt/nuxt · closed18 months ago · 37% similar

3.xpending triage

useFetch return type with POST method

nuxt/nuxt · closed26 months ago · 36% similar

3.xpending triage