fix(core): update chainId retrieval logic to consider syncConnectedChain configuration

[yigiterdev]

Problem

Fixes #4680
Generated hooks from wagmi-cli were ignoring the syncConnectedChain configuration setting and always prioritizing the connected account's chainId over the config's default chainId. This meant that setting syncConnectedChain: false had no effect on generated hooks, requiring users to explicitly provide a chainId parameter to every hook call when they wanted hooks to work regardless of the connected network.

Solution

Updated the chainId resolution logic to respect the syncConnectedChain configuration:

Behavior after fix:

When syncConnectedChain: true (default): Uses account.chainId if available, falls back to configChainId
When syncConnectedChain: false: Uses configChainId directly, ignoring connected account's chain

[changeset-bot]

⚠️ No Changeset found

Latest commit: ffaf19c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
wagmi	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2025 3:20pm