Misleading error message in useFetchnuxt/nuxt 路 updated2 years ago 路 33% similar enhancementworkaround availableupstream馃嵃 p2-nice-to-have
Page is rendered even if `fetch` called `redirect`nuxt/nuxt 路 closed3 years ago 路 33% similar available soon2.x
`useFetch`'s data type is `any` in `<template>` but correct in `<script>`nuxt/nuxt 路 closed3 years ago 路 32% similar 3.xpending triageneeds reproduction
Unable to get the full error message when using useFetch() or $fetchnuxt/nuxt 路 closed2 years ago 路 32% similar 3.xpending triage
If a component uses empty data in `useFetch`, then `clearError` will be invalidatednuxt/nuxt 路 closed2 years ago 路 32% similar 3.xpending triage
`useFetch` returns the `.data` property as `any`nuxt/nuxt 路 closed3 years ago 路 32% similar 3.xpending triage
Add a way to distinguish between server error/nonerror responses for client typesnuxt/nuxt 路 closed2 years ago 路 32% similar pending triage
To redirect in middleware hook makes `write after end` error. (with Vercel)nuxt/nuxt 路 closed3 years ago 路 32% similar 3.xpending triage
ERR_REDIRECT is thrown by default, leads to confusing behaviornuxt/nuxt 路 closed3 years ago 路 32% similar pending triage2.x