Content pfp
Content
@
0 reply
0 recast
0 reaction

Joaquim Verges pfp
Joaquim Verges
@joaquim
`npm i thirdweb` that's it. that's all you need. Everything you can ever wish for for your web3 frontend in ONE package. We just released the stable version today! https://portal.thirdweb.com/typescript/v5
24 replies
12 recasts
236 reactions

arod.buidler pfp
arod.buidler
@arod
Is this similar to wagmi? Do you know the trade-offs for moving to it, or do you have some articles comparing?
1 reply
0 recast
0 reaction

Joaquim Verges pfp
Joaquim Verges
@joaquim
Check out the feature comparison matrix and benchmarks here: https://portal.thirdweb.com/typescript/v5/why-thirdweb Main advantage is the out of the box performance (pro RPC built in) + wallets (350+ supported wallets including embedded wallet+ account abstraction) + UI components
1 reply
0 recast
2 reactions

arod.buidler pfp
arod.buidler
@arod
Thanks! I'll give it a chance. I love their CLI for generating custom-typed functions based on the ABI (https://wagmi.sh/cli/getting-started), which helps me a lot in the development. I saw there is a CLI on this comparison table.
1 reply
0 recast
1 reaction

Joaquim Verges pfp
Joaquim Verges
@joaquim
Yep, try out `npx thirdweb generate <chainId>/<contractAddress>` You don't even need an abi at all! Works with any deployed contract. The generated code is written to your sex, shadcn style. Type safe and optimized. Includes all functions and events. https://portal.thirdweb.com/typescript/v5/extensions/generate
2 replies
0 recast
0 reaction

Joaquim Verges pfp
Joaquim Verges
@joaquim
Then for each function generated, you can use 'useReadContract' and pass it the function to 'react-ify' the function. For writes you just use 'useSendTransaction' normally. Check out https://catattack.thirdweb.com/ for a live website using this. GH repo in footer!
1 reply
0 recast
1 reaction

arod.buidler pfp
arod.buidler
@arod
wagmi works like that too, but for local development, I use the ABI once it's not deployed yet.
0 reply
0 recast
0 reaction