DEV Community

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

Posted on

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-baked and call it done.

Looking for contributors

If you've been frustrated by the same problem — or if you have opinions about auth, CI setup, Docker, tRPC vs REST, or monorepo structure — I'd love your input. Open an issue, start a discussion, or just drop a star if the idea resonates.

GitHub logo AmitGharge / stackweave

Production-ready full-stack monorepo: Next.js + Expo + Express with Turborepo. Type-safe from database to UI.

StackWeave

License: MIT TypeScript Next.js Expo Turborepo

A production-ready, full-stack monorepo template with Next.js, Expo, and Express - built for speed and developer experience.

The Problem

Building full-stack applications with web and mobile frontends requires:

  • Managing separate repositories or messy codebases
  • Duplicating types, API logic, and configurations
  • Version conflicts between shared dependencies
  • Manual synchronization of schema changes across platforms

What StackWeave Solves

Single Source of Truth - Shared types, API client, and database schema
Native Development - Each platform uses optimal tech (Next.js for web, Expo for mobile)
Shared Styling - Consistent design system via shared Tailwind config
Type Safety - End-to-end TypeScript from database to UI
Fast, Cached Builds - Turborepo inte

First-time contributors welcome! Check out issues labeled good first issue.

This is an open-source project…

Top comments (0)