Add Support for all (Viem) Chains

[bh2smith]

User description

Instead of having a finite supported chain list, we now support all chains provided by viem.

---

PR Type

enhancement, dependencies

---

Description

• Replaced individual chain imports with a wildcard import from viem/chains.
• Updated SUPPORTED_NETWORKS to include all chains exported by viem, allowing dynamic support for any new chains added by the viem library.

---

Changes walkthrough 📝

	Relevant files
Enhancement	network.ts Support all chains exported by `viem` in network configuration src/network.ts Replaced individual chain imports with a wildcard import from viem/chains. Updated SUPPORTED_NETWORKS to include all chains exported by viem. +3/-25

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Dynamic Import Check Ensure that the dynamic import of all chains from viem/chains using wildcard import and subsequent usage in SUPPORTED_NETWORKS does not introduce any runtime errors or issues with missing or undefined chain configurations.

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Add validation for the 'chains' object to ensure it contains valid data Consider validating the chains object before using it in createNetworkMap. This ensures that the object is not empty and contains valid data, preventing runtime errors if the import fails or the data structure is not as expected. src/network.ts [5] +if (!chains || Object.keys(chains).length === 0) { + throw new Error("No chains found or invalid chains object."); +} const SUPPORTED_NETWORKS = createNetworkMap(Object.values(chains)); Suggestion importance[1-10]: 9 Why: This suggestion adds a crucial validation step to ensure that the 'chains' object is not empty or invalid, which can prevent potential runtime errors. This is a significant improvement in terms of robustness and error handling.	9
Possible bug	Handle cases where 'Object.values(chains)' might return an empty array in 'createNetworkMap' Ensure that the createNetworkMap function handles cases where Object.values(chains) might return an empty array, which could lead to unexpected behavior if not handled properly. src/network.ts [5] -const SUPPORTED_NETWORKS = createNetworkMap(Object.values(chains)); +const networkValues = Object.values(chains); +const SUPPORTED_NETWORKS = networkValues.length > 0 ? createNetworkMap(networkValues) : {}; Suggestion importance[1-10]: 8 Why: This suggestion ensures that the 'createNetworkMap' function handles empty arrays gracefully, preventing potential issues. It is a valuable addition for robustness.	8
Best practice	Add a type definition for the 'SUPPORTED_NETWORKS' variable to enhance readability and maintain type safety To enhance readability and maintainability, consider adding a type definition for the SUPPORTED_NETWORKS variable. This will help developers understand what kind of data structure they are working with and ensure type safety. src/network.ts [5] -const SUPPORTED_NETWORKS = createNetworkMap(Object.values(chains)); +type NetworkMap = Record<string, Chain>; +const SUPPORTED_NETWORKS: NetworkMap = createNetworkMap(Object.values(chains)); Suggestion importance[1-10]: 7 Why: Adding a type definition improves code readability and maintainability by making the data structure explicit. This is a good practice but not as critical as runtime validation.	7
Enhancement	Add a unit test to verify the integrity and completeness of the 'SUPPORTED_NETWORKS' map To ensure that all networks are correctly supported and initialized, consider adding a unit test that verifies the integrity and completeness of the SUPPORTED_NETWORKS map. src/network.ts [5] -const SUPPORTED_NETWORKS = createNetworkMap(Object.values(chains)); +// Example unit test +describe('Network Map Initialization', () => { + it('should correctly initialize all supported networks', () => { + const expectedNetworks = Object.values(chains); + const actualNetworks = Object.keys(SUPPORTED_NETWORKS); + expect(actualNetworks.sort()).toEqual(expectedNetworks.sort()); + }); +}); Suggestion importance[1-10]: 6 Why: Adding a unit test is beneficial for ensuring the integrity of the 'SUPPORTED_NETWORKS' map. While it is an enhancement for testing, it is not as critical as runtime checks or type definitions.	6