Advanced
Aaron Ho@aho
4/27/2023

Devs using monorepos, when and how do you use them?

In reply to @aho
pugson (mike rainbow)@pugson
4/27/2023

i don't think i've ever been in a monorepo that didn't suck

In reply to @aho
Dan Romero@dwr
4/27/2023

we use a monorepo for both hubs and warpcast apps

In reply to @aho
Colin Armstrong@colin
4/27/2023

We use a monorepo for our frontend and backend. Sharing code is easier

In reply to @aho
Colin Armstrong@colin
4/27/2023

Google uses a monorepo for 100% of their code. Pretty neat

In reply to @aho
luke miles@worm
4/27/2023

We have all of our code in one repo. It's just easier. See a line of copy I want to change? Grep the whole repo for it, find it

In reply to @aho
Greg Skriloff@greg
4/27/2023

Backend + frontend when it can’t be done together in something like Next.js but I’m not likely to use the backend anywhere else. Here’s a recent example https://github.com/gskril/ens-adoption

In reply to @aho
Pierrick@pierrick
4/27/2023

Using Lerna in this one: https://github.com/pooltogether/v4-autotasks It's great when you want to share helper functions across various packages. You don't have to go update each repo one by one.

In reply to @aho
Alberto Ornaghi@alor
4/27/2023

A monorepo with well-organized sub directories is the same as having different repos. But better. You are always sure to have the latest version of each component.

In reply to @aho
vern@vern
4/27/2023

We use monorepo for our nodejs backend code with turborepo. Multiple services with shared utils + models. Single, unified CI flow for automated builds and deploys. Major benefits imo

In reply to @aho
David Furlong@df
4/27/2023

reusing code across discove web, react-native and backend services

In reply to @aho
osama@osama
4/27/2023

contracts+f/e+subgraph in monorpo works just fine™️ (powered by turborepo, next, forge, typechain)

In reply to @aho
maurelian@maurelian
4/27/2023

Optimism uses a monorepo. We have many packages and services that need to be updated simultaneously to stay in sync. It also makes it easier to run Integration tests and manage CI. For us I can’t imagine how we would function without a monorepo.

In reply to @aho
Carlos Matallín@matallo
4/27/2023

We do at Shopify, here’s a good example https://github.com/Shopify/polaris

In reply to @aho
tim 🥝@timdaub
4/28/2023

My rating - building a monolith: cool, why not - building microservices: cool, why not - building as many packages: cool, why not - building many packages as monorepo: why? Just whyyyyy? And yes, „oh but Google does it“ isn‘t a technical argument u fukin LARP

In reply to @aho
Joe Blau@joeblau
4/28/2023

Unless you’re a big org with people dedicated to making this work, don’t do it. This is the modern version of “MSFT had their meetings on the 3rd floor so we should too” type of thinking. We used one at Uber ATG, I loved it, but it requires a lot of work.

In reply to @aho
GabrielAyuso.eth ⌐◨-◨@gabrielayuso
4/28/2023

I've been working pretty much exclusively in a monorepo for the past 9 years. When I don't, I wish I were in a monorepo.

In reply to @aho
Axel@ax
4/28/2023

When? Always! Amazing for universal apps + design system: https://github.com/showtime-xyz/showtime-frontend

In reply to @aho
ren (wassie arc)@ren
5/2/2023

i think most startups should probably just mono repo, its good and convenient for managing products with many services (<20)