A place for developers to talk about building on Farcaster.

/dev

Writer. Building @pinatacloud. Working on simple static site hosting https://orbiter.host \ https://polluterofminds.com

Gotta side with @gregfromstl; mono repos give the ick 

@polluterofminds and I have been using this stack lately for Pinata and other projects like Orbiter:

name-client (Vite + React)
name-backend (Hono on a Cloudflare Worker)
name-contracts (foundry) 

Clean, simple, and easy for either of us to jump into and work on

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

How do you share ABIs and API types? Being able to have all of those in the same repo has been a huge speed boost for me personally

likes building things • https://alexgrover.me/links

Those approaches aren’t mutually exclusive - for example you can share the request/response schemas (using eg zod) and then get type inference that your request body conforms to what it thinks the backend expects. The backend still needs to validate the payload, but at least TS can help make the DX better

I'd argue they shouldn't. Your backend should parse inputs and your app should parse responses from the backend. It's safer that way

And you say MONOREPOS give the ick??? 🤣

Copy and paste 😅 That would be one benefit of a mono repo

Very monorepo-pilled for this reason. Full stack type inference is just absurdly productive