blockchatting VS TypeChain

The contract itself is quite simple as you can see, it is on the client-side that much of the heavy lifting goes on. You can check the source code of the contract here. It also has tests implemented with Hardhat + TypeScript.

In the two previous posts of this serie, we have learned how to build a house-swap ethereum smart-contract using solidity and how to test it using hardhat. In this post, we will create an angular application and we will install ethers to interact with the smart-contract and ethers-typechain to generate typescript types from our contract json abi.

For the wallet connection, we use WAGMI. The chat contract is connected within a React context, so that all components can interact with it. Contract interactions are also type-checked via TypeChain. These types are created on the contract development phase, but you can easily copy & paste them to your types directory at frontend, or wherever you store them.

Two parts are generally independent, except when it comes to typing. To ease contract interaction, TypeChain generates types for each contract, which can be accessed by both the Frontend and Contracts parts.

Uses typechain to auto-generate typescript bindings for compiled contracts, useful for auto-completion in your frontend dApps

Typechain GitHub Repository

AFAIK it's used quite a lot in web3, especially with React apps. Also check TypeChain ;) https://github.com/ethereum-ts/TypeChain

I can also recommend Typechain (https://github.com/ethereum-ts/TypeChain) separately or in combination with HardHat (https://hardhat.org).

Have you checked out Typechain? https://github.com/ethereum-ts/TypeChain

You can check TypeChain that creates abstraction over contracts connection based on ABI that you provide. You can find ABIs for your contract in the Hardhat build folder.