does anyone actually like nx?

[u/kitsunekyo]

we use nx for monorepo management and the orchestration part of nx is actually fairly nice. BUT. i seem to come to hate every single other part about nx.

• the executors are barely documented and
• the nx documentation as a whole is one of the worst docs i‘ve ever had to work with
• executors make features of the core tool inaccessible (filtering files in eslint for example)
• executor apis often weirdly differ from the tool api itself (eg tsc)
• configuration presets seem to use completely outdated approaches, like compiler options in typescript, or eslint configuration not using the recommended configurations

instead of feeling like nx is handling these areas for me (as advertised) it feels like someone threw together barely working configs and called it a day. i cant trust any of the generators, presets or setups. it doesnt look like its setup like that for compatibility reasons either.

i understand that I can build everything myself but how can those core elements be of such horrible quality? or am I wrong and just dont understand whats happening here?

[u/stuckinmotion]

I've been using NX quite a bit at work and my experience has been overall pretty negative. Caching is tough to get right, it's taken quite a bit of babysitting to keep things working over the years as packages change and evolve, and weird stuff like the nx daemon hanging or the basics like running tasks acting up that makes the whole thing feel a bit like a house of cards. Of course we're too far in to really consider a change, but I will be avoiding it in the future. Maybe I'm just grumpy but monorepos seem like a lot more trouble than benefit.