StackWeave - a fullstack monorepo for web, mobile & backend (and why I built it)

The problem Every time I started a new project that needed a web app, a mobile app, and a backend API, I ended up with three separate repos, three package.json files, and the same types copy-pasted across all of them. Schema changes meant touching three places. Dependency versions drifted. It was slow and painful. What I built StackWeave is a monorepo template that puts Next.js (web), Expo (mobile), and Express (backend) under one roof - managed by Turborepo and Yarn v4 workspaces. Shared packages handle types, the API client, validators, the Prisma DB layer, and even the Tailwind config - so a schema change or a type update ripples through everything at once, safely. Where it stands It works — you can clone it, run yarn dev, and have all three apps running in under 5 minutes. But it's still early. Auth, a CI/CD pipeline, Docker Compose for local Postgres, and a proper docs site are all missing. That's intentional — I'd rather build those with the community than ship something half-bak