Nuxt · NUXT0035
Do not shadow Nuxt useFetch
Flags conflicting useFetch import in Nuxt imports code before it leaks into runtime behavior.
nuxt/imports/no-conflicting-usefetch-importsrc/rule-packs/nuxt/rules/nuxt/no-conflicting-use-fetch-import.ts Upstream docs Run this rule
pnpm nuxt doctor --rules nuxt/imports/no-conflicting-usefetch-import
Why it matters
Nuxt data fetching relies on stable keys, payload serialization, and request context. Bypassing those contracts can duplicate requests or lose SSR data.
Recommended fix
Remove conflicting useFetch import, or move it to the Nuxt runtime/API that owns that behavior.
Useful links
Example
Avoid conflicting useFetch imports
Before
import { useFetch } from '@vueuse/core'
const { data } = useFetch('/api/user')
After
import { useFetch as useVueUseFetch } from '@vueuse/core'
const { data } = await useFetch('/api/user')