fix: wagmiConfig override matches SE-2 main client + arbitrum#122
Merged
Conversation
The previous override replaced the base wagmiConfig client with a simpler function that didn't reference hardhat, DEFAULT_ALCHEMY_API_KEY, or ScaffoldConfig, leaving them as unused imports under next 16 + eslint-config-next 16 strict no-unused-vars. Align the override with scaffold-eth-2 main's client logic (rpcOverrides + isUsingDefaultKey ordering + hardhat pollingInterval) and layer the arbitrum custom-RPC branch on top.
This file contains hidden or 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
1 participant
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.
Why
After scaffold-eth/create-eth's upcoming backmerge (PR #427), the generated nextjs uses next 16 + eslint-config-next 16, which enables a stricter `@typescript-eslint/no-unused-vars`. The current wagmiConfig override replaces the base client with a simpler function that doesn't reference `hardhat`, `DEFAULT_ALCHEMY_API_KEY`, or `ScaffoldConfig` — those become unused imports and `yarn next:lint --max-warnings=0` fails.
What
Align the override with scaffold-eth-2 main's wagmiConfig client (rpcOverrides + isUsingDefaultKey RPC ordering + hardhat pollingInterval skip) and layer the arbitrum custom-RPC branch on top of it. Variable names and logic now match the scaffold main branch.
Test plan
🤖 Generated with Claude Code