Hello! I used to like NX a lot. It was a monorepo for all my projects—different brands and clients in one place. It worked well, but it didn’t suit me. Most of my projects are single Angular apps. So, I stopped using one big NX repo and made separate projects instead. Here’s why I prefer it.
Monorepo Problem
NX was good for sharing libraries and components between projects. I put everything in it—a dashboard for one client, a storefront for another. I wanted to reuse code. But it was hard to keep everything compatible and updated. For projects that don’t change, this was too much work. Also, NX features like affected builds and caching didn’t help much with single apps.
Standalone Is Easier
Now, each project has its own repo. It’s simple and clear. I use WakaTime (see my profile) to track my time on each one. With separate projects, the numbers make sense—no confusion from a monorepo. It’s fast to start and easy to change. This is how I like to work.
NX for Some Cases
I still use NX sometimes. For projects with a NestJS API and an Angular frontend, a monorepo is great. Sharing code works there. But putting all my client projects in one big NX repo was a mistake.
What I Learned
I’ve worked on many projects—small teams and big ones. I like tools that fit the job. Separate repos are simple. WakaTime shows me my time. NX is good when I need it. That’s what works for me now.
Top comments (0)