Misleading error message in useFetch
enhancementworkaround availableupstream馃嵃 p2-nice-to-have
# Misleading error message in useFetch
Components tests it is triggering global route middleware
vitest-environment
useFetch is fired twice if server returns with a 500 Error
3.xpending triage
Unable to get the full error message when using useFetch() or $fetch
3.xpending triage
useFetch request status is error, data is null
3.xpending triageneeds reproductionclosed-by-bot