Just take a look at their "enforce-module-boundaries" EsLint rule, and you'll have a very good starting point to understand this topic.
I'm using Nx for more than five years now, and it changed everything in the way I architect apps, from simple Front-Ends, to MFE, to complex distributed systems (Nx is language and platform-agnostic, and if you don't find a plug-in for your stack, you just need to know a little bit of ES6+ or Typescript and use their API to write one that suits your needs).
As you can (and must) read in their docs, using Nx drives you to a whole different mental model when you think about your system. After a little bit of practice, you naturally think in a "Modular Clean Architecture" way :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Just take a look at their "enforce-module-boundaries" EsLint rule, and you'll have a very good starting point to understand this topic.
I'm using Nx for more than five years now, and it changed everything in the way I architect apps, from simple Front-Ends, to MFE, to complex distributed systems (Nx is language and platform-agnostic, and if you don't find a plug-in for your stack, you just need to know a little bit of ES6+ or Typescript and use their API to write one that suits your needs).
As you can (and must) read in their docs, using Nx drives you to a whole different mental model when you think about your system. After a little bit of practice, you naturally think in a "Modular Clean Architecture" way :)