Post

For monorepos, use pnpm.

Moi J

@moi-j.bsky.social

13 Dec 2025

I would love to know why 🙏

Juri

@juri.dev

It is just superior - faster (due to package cache and smart symlinking) - pnpm catalogs to avoid version conflicts - "workspace:*" protocol is just more explicit & clear - security features like postinstall prevention/delay etc. 👆 things that immediately come to my mind. Just less surprises

13/12/25, 3:31 pm0 reposts5 likes

Sean Newell

@sean.thenewells.us

13 Dec 2025

Yarn also uses "workspace:*" package refs, can confirm very nice. Wish we were using pnpm tbh.

Sam 💛

@samhh.com

13 Dec 2025

I’m curious, do catalogs achieve anything more than I get with pnpm up -r?

Juri

@juri.dev

13 Dec 2025

It's more about control. In particular in a monorepo you might want to sync certain versions while keeping others dependent per project. It's basically a really nice way to do some sort of hybrid single-version policy in a monorepo setup

pnpm.ioCatalogs | pnpm"Catalogs" are a workspace feature for defining dependency version ranges as reusable constants. Constants defined in catalogs can later be referenced in package.json files.