Viem package - minor version bump causes breakage?

[zeuslawyer]

needs investigation

It appears that installing the latest version (as of date of writing) of viem i.e. 2.23.12 instead of v2.21.25 causes the writeContract method in to fail as reported in this PR
#7

[SyedAsadKazmi]

@zeuslawyer, the issue persists regardless of the viem version.

Thanks.

[zeuslawyer]

Ack @SyedAsadKazmi . Marked as needs investigation.

[SyedAsadKazmi]

How to Reproduce?

Steps

To reproduce the issue, add the following lines to the packages/ccip-js/test/integration.test.ts:

1. Firstly, add the imports and keys:

    import { sepolia } from 'viem/chains'
    import { privateKeyToAccount } from 'viem/accounts'
   
    const SEPOLIA_ACCOUNT_PRIVATE_KEY = "0x_PRIVATE_KEY" // The account should have some Sepolia-ETH to pay for gas
    const ALCHEMY_SEPOLIA_RPC_URL = "https://eth-sepolia.g.alchemy.com/v2/ALCHEMY_API_KEY"

2. Then, add this test to the '√ approve' (i.e., inside the describe('√ approve', () => {}) fragment):

    it('√ should succeed when actual wallet client is used', async () => {
   
     const { bridgeToken, localSimulator, router } = await getContracts()
   
     // Actual wallet client on Ethereum Sepolia created using the private key
     const walletClient = Viem.createWalletClient({
       chain: sepolia,
       transport: Viem.http(ALCHEMY_SEPOLIA_RPC_URL),
       account: privateKeyToAccount(SEPOLIA_ACCOUNT_PRIVATE_KEY),
     })
   
     const approvedAmount = parseEther('10')
   
     // CCIP: Approval Transaction
     const ccipApprove = await ccipClient.approveRouter({
       client: walletClient,
       routerAddress: router.address,
       amount: approvedAmount,
       tokenAddress: bridgeToken.address,
       waitForReceipt: true,
     })
   
     console.log(ccipApprove?.txHash)
   
     expect(ccipApprove).toBeDefined()
   
     console.log('\u2705 | Approves with valid input when actual wallet client is used')
   }, 60000) // increased the timeout to 60s because, by default, it's only 5s, which could potentially cause a timeout

Results

1. Executing the matching tests for √ approve on the main branch:

    npx jest -t "√ approve"

   

2. Executing the matching tests for √ approve on the fixes branch (i.e., the branch from my forked repo used for the PR):

    git checkout fixes
    npx jest -t "√ approve"

   

[zeuslawyer]

This has been fixed in #12

Thank you for your help in identifying issue and fixes @SyedAsadKazmi .