NX can give you more power than you think: why I use it in all JS projects

I have been using NX in almost all my projects for several years and it improves my productivity and DX a lot. Nevertheless I still see a lot of myths and misunderstandings about the use of this tool. And even teams that use it for a while often do not get all the benefits. So, I decided to show what approaches I personally use with NX for both small pet-projects and enterprise development to maximize dev experience, clean code and resource optimization.

Usage for a small project

People often say that they don’t need NX because they have different repos for projects. They think monorepo is about one big repo that is used by the whole big corpo to let thousands of people work together.

But in this case, monorepo is just a way to organize your project. The project can be very small and made by one person. It is not harder to support once you have this experience, gives you all the benefits and often even saves you some time. The cool thing is that all the patterns you use for organizing this small monorepo are the same if you work on a big project with a team or even if you have a big repo for several projects and teams working at the same time. You can just use the same methods of repo management instead of thinking about project organization every…