chore: incrementally upgrade to nextjs app router #1513
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1483
We are currently stuck with this issue rainbow-me/rainbowkit#1777, once we resolve it, i'll bring back
connectorsand pack this PR.Small issues we are left with:
connectorsWe are blocked at this moment with the last item, the only solution here is to use list of connectors from the wagmi https://wagmi.sh/react/api/connectors#available-connectorsWe have 2 wagmi config files now, one that we pass to the client-side components and one for the server-side components, issue is that we cannot pass a wagmi config file with rainbowkit connectors to the server-side components, therefore, whenever we do anything related to the contracts in the server-side component, we would use wagmi server config.