Fix: Replace deprecated connect() in useScaffoldContract hook

[Einarmig]

Fix: Contract Connection Error in useScaffoldContract Hook

Problem

The application was crashing when users connected their wallet and navigated to the "My NFTs" section with the following error:

Error: contractInstance.connect is not a function

Error Location: hooks/scaffold-stark/useScaffoldContract.ts:43

Root Cause

The useScaffoldContract hook was using the deprecated .connect() method from starknet.js v6.x API, which no longer exists in starknet.js v8.x.

Old Code (Broken)

const contractInstance = new Contract({
  abi: deployedContractData.abi as Abi,
  address: deployedContractData.address,
  providerOrAccount: publicClient,
});

if (account) {
  contractInstance.connect(account); // ❌ This method doesn't exist in v8
}

Solution

Updated the contract instantiation to use the new starknet.js v8 API, where the account is passed directly in the constructor instead of using a separate .connect() call.

New Code (Fixed)

const contractInstance = new Contract({
  abi: deployedContractData.abi as Abi,
  address: deployedContractData.address,
  providerOrAccount: account || publicClient, // ✅ Pass account directly
});

Impact

• ✅ Users can now connect their wallet and access "My NFTs" without crashes
• ✅ Contract instances properly use the connected account when available
• ✅ Falls back to read-only provider when no wallet is connected
• ✅ Compatible with starknet.js v8.5.3

Files Changed

• packages/nextjs/hooks/scaffold-stark/useScaffoldContract.ts

Testing

1. Connect wallet to the application
2. Navigate to "My NFTs" section
3. Verify no runtime errors occur
4. Verify NFTs load correctly

Types of change

• Bug