Error: No QueryClient set, use QueryClientProvider to set one
TanStack Query hooks ran outside a QueryClientProvider (or a duplicate copy of the library is installed).
Exact message you may see
No QueryClient set, use QueryClientProvider to set one
Seen on:
React
Meaning
useQuery needs the client from context. Missing provider, tests without it, or two versions of @tanstack/react-query (separate contexts) cause it.
Common causes
- QueryClientProvider missing at the root
- Tests rendering without a provider
- Duplicate library versions / monorepo duplicates
⚡ Quick fix
- Wrap the app in <QueryClientProvider client={queryClient}>
- Provide a wrapper in tests
- Deduplicate with npm ls @tanstack/react-query
Detailed fix by platform
React
- jsx
const queryClient = new QueryClient(); <QueryClientProvider client={queryClient}><App /></QueryClientProvider>
How to diagnose
- Provider — At the root?
- Copies — One library version?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in React
- Objects are not valid as a React child Error: Objects are not valid as a React child
- Functions cannot be passed Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".
- Module parse failed Module parse failed: Unexpected token. You may need an appropriate loader to handle this file type
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 12 Oct 2026