A place for talking about the Ethereum Virtual Machine on Farcaster.

Hi, I made a library that spins up a front-end for you to interact with your contracts while in development. The UI is generated from your compiled contract artifacts. Supports Hardhat and Foundry.

Demo: https://www.youtube.com/watch?v=s5IMzkf2uak
Package: https://www.npmjs.com/package/@type_of/contract-gui

The fun, simple, & secure way to explore web3, NFTs, and Ethereum 🌈  We’ve moved accounts to @rainbow! 

TypeScript Interface for Ethereum ~ viem.sh

Engineer on Base 🔵 • Building BlockSocks 🧦 • Denver, CO 📍

Oh, and this is all built on top of Rainbowkit and Wagmi/Viem, so huge shoutout to @rainbowdotme @viem @mikedemarais.eth @jxom

...and the guy that made shadcn/ui.

build, lift, & coffee | ENS Steward | namestone.com | slobo.xyz

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

Haha, nice. I was also looking for something like this recently and the only thing I found was super out of date.

scaffold-eth-2 comes with something like this and it's pretty great, but it's not standalone.

yooo this is great! @slobo.eth you were asking if this existed recently

𝓓𝓲𝓼𝓽𝓲𝓷𝓰𝓾𝓲𝓼𝓱𝓮𝓭 Engineer at C̶o̶i̶n̶b̶a̶s̶e̶ Yahoo. Yes

Building Design Systems and frontend tools at your favorite internet company like it’s 1999.

Ty dude! Just solving my own problems over here 🤙

There is a lot to unpack here. 
Literally, you committed 400+ files totaling 280+MB of .next cache to the pkg.
Also, block explorers support uploading custom ABIs you can probably make a command to auto-upload and have a UI.
IMO for contract development testing scripts are the preferred way of interaction.

Software developer, open source enthusiast, privacy advocate.

Clear Wallet Open-source privacy focused wallet: https://clear-wallet.flashsoft.eu/


No .next folder should never be included in npm pkg is meant to only exist on local dev machine. 

Use .npmignore file to ignore that folder for your next version of the pkg.

I mean, yeah, the library is a built Next.js project, so that's expected. It's meant for local development so file size shouldn't matter IMO. Also, since it's primarily for local dev, block explorers wouldn't work.

> testing scripts are the preferred way of interaction

IMO, having options is good.