-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: adjust legacy installation dependencies #93
Comments
Hey @heronlancellot I'd like to work on this |
hey yo @blackbeard002 ! Assigned to you ! |
Any progress on this submission @blackbeard002 ? I know its quite hard ! |
Hey @0xneves won't be able to fix the issue on time. Could you unassign me? |
hey yo @blackbeard002 ! Perfect man, thanks for letting us know !! 🙏 🙏 |
@0xneves I solved this task, if you give it to me, I can commit. The problem is, to solve this, wagmi and its dependencies were updated and with that, the documentation changes from version v1 to v2. In v2, the code that is present in wallet.config will be changed, which in this case would be a new task beyond this one. |
Thank you @gabrieljolvm for using your valuable time on this issue. |
hey yo ! any update of this issue @gabrieljolvm ? |
Sorry, i'll update this issue until tomorrow. @heronlancellot |
Hey I was just taking a look, seems like this is solved. I've checked out the |
Refactor Request
Describe the Refactor Request
The Definition of done is implementing
npm i
and check if the dApp works perfectly.Describe Preferred Solution
Check out the packages, like
@rainbow-me/rainbowkit-siwe-next-auth
and the others.The repo should work perfectly without running legacy-peer-deps.
Fix the package.json
Describe Alternatives
If have any other solution or improvement, let us know ! 🙏✌️
Related Code
package.json
The text was updated successfully, but these errors were encountered: