18
What's the consensus on monorepo tooling in 2024? (lemmy.blackeco.com)
submitted 8 months ago by BlackEco@lemmy.blackeco.com to c/javascript@programming.dev
4 comments fedilink hide all child comments

Hello all,

My company is looking into building a new app from scratch based on Next.js with a few modules on the side (batch jobs, utility services, etc.)

Our current monorepo has been started over 4 years ago with Yarn Classic + Lerna and I was wondering what is the current consensus for building a monorepo, considering that the landscape has evolved greatly since then (npm now supports workspaces, pnpm has gained in popularity, Yarn has been re-engineered and multiple build systems have been released)

I would greatly appreciate if you have some comparison between package managers and build systems you could link to.

you are viewing a single comment's thread
view the rest of the comments
[-] dracs@programming.dev 5 points 8 months ago

We're still using Yarn and Lerna on our projects at work. We're about to start a fresh new build though and have been looking at NX for the new setup. From our PoCs it works a lot better. Lots less rebuilding and bootstrapping with it's built-in caching. Looking forward to implementing it properly.

Still want to look into Yarn 2 and see if it works with it.

[-] BlackEco@lemmy.blackeco.com 2 points 8 months ago

I took a look at NX, they seem to limit some features (like NX Agents) to their Cloud offering, don't they?

[-] dracs@programming.dev 1 points 8 months ago

They do. I haven't tried out their cloud offering yet. Even without that though, I've found the builds running faster with just their change detection and caching systems.

this post was submitted on 07 Mar 2024
18 points (100.0% liked)

JavaScript

1700 readers
1 users here now

founded 1 year ago
MODERATORS
erlingur@programming.dev
Ategon@programming.dev
nick@programming.dev