Closed Spencer-Sch closed 2 weeks ago
@Spencer-Sch These are just peer dependencies warnings that are coming from @metamask/sdk
dependency which is used by wagmi
. Those warnings shouldn't cause any errors in your app.
Regarding your Can't resolve 'pino-pretty'...
error, this comes from the WalletConnect SDK which is also used by wagmi
. You would need to configure your next.config.js
like this https://github.com/rainbow-me/rainbowkit/blob/main/examples/with-next-app/next.config.js
Let me know if this helps 👍
Thank you for your reply, @magiziz!
I wish I had known the warnings could be safely ignored before I spent multiple hours trying to solve it 🤦♂️.
That's ok though, because your suggestion about next.config.js
has made all the "Import trace" and "Module not found" messages disappear!
Thank you again!
Is there an existing issue for this?
RainbowKit Version
2.1.2
wagmi Version
2.10.2
Current Behavior
After executing
npm install @rainbow-me/rainbowkit wagmi viem@2.x @tanstack/react-query
to add RaindbowKit to existing Next.js project I get the following error:When running
npm run dev
I get the following error:The project builds and displays on localhost:3000. The RainbowKit ConnectWallet component renders and functions as expected.
Expected Behavior
I expected for Next.js to build and run locally without any dependency issues.
Steps To Reproduce
npx create-next-app@latest
npm run dev
localhost:3000
in browser (I'm using Chrome)ctr+c
theny
thenenter
npm install @rainbow-me/rainbowkit wagmi viem@2.x @tanstack/react-query
ConnectWallet
component to project as directed by the RainbowKit documentation. (https://www.rainbowkit.com/docs/installation#import)npm run dev
localhost:3000
in browser (I'm using Chrome)Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
https://github.com/Spencer-Sch/next-rainbowkit-issue-recreation
Anything else?
Next.js with RainbowKit libs was all working properly last week. It was all working properly earlier today as well until I tried to add DaisyUI to the project. That's when I started seeing this peer dep conflict about i18. However, the issue has persisted even in brand new project installs without the addition of DaisyUI.
Package.json![package-json](https://github.com/rainbow-me/rainbowkit/assets/78219375/60127b38-735e-4761-8c03-2a09506406d1)