Uncaught Error: No QueryClient set, use QueryClientProvider to set one when using hook useEnsName

[web3dopamine]

After following the docs for useEnsName : https://wagmi.sh/react/hooks/useEnsName

i get the following error

[tmm]

Did you wrap your app inside WagmiConfig?

[tmm]

@agalbulescu if you you create a minimal reproduction using new.wagmi.sh, I'm happy to look into it.

[agalbulescu]

@tmm thanks, meanwhile I found the issue, it was from the naming I was using in the WagmiConfig component parameter, when upgrading to wagmi 1.x.x I switched from "client={config}" to "config={config}" and had the issue. Once I changed it to "config={wagmiConfig}" it all worked fine. A quick side-note as I bumped into this following issue after fixing the first one, walletconnect also changed to v2 and to be able to connect to the WebSocket, you have to pass a project ID you can get from the walletconnect website, just make sure the environment variable is accessible from the front-end, in my case (Next.js) I had to use process.env.NEXT_PUBLIC_PROJECT_ID.
Thanks again for your help!

[nadiia-balaian]

Having the same issue. I used react-query in my application, but version 3.x.x.
I decided to migrate from wagmi 1.x to wagmi 2.x. After that I made migration to react-query 5.x. So I expect everything should work fine, cause I had QueryClientProvider before.
Now application is wrapped with WagmiProvider and QueryClientProvider.
When I use hook useAccount application works fine, but when I add useConnect or useEnsName application crashes with an error.
I tried to use different order, tried to wrap components separately.
I would appreciate help or hint what else should I check

[kaushikriya]

@nadiia-balaian Did you manage to resolve this issue? I'm facing the same issue

[Likang0122]

尝试升级下Node版本试试
如：v20.10.0或更新版本

[dev-pyoungwoo]

Recently, while implementing a DApp using Web3Modal v4 and the latest version of wagmi, I encountered the same issue.
I resolved this by modifying the settings in the tsconfig.json file.
The changes I made were to set "module" to "ESNext" and "moduleResolution" to "bundler".
"module": "ESNext", "moduleResolution": "bundler",
It has been a long time since the question was posted, but I hope it helps someone eventually.