We’re migrating off of Nx currently because the upgrade path got too tenuous.

• Recent namespace changes made a hard dependency jump
• Difficult to do unique things with our Next build
• Didn’t easily upgrade with Next, which already does a lot to optimize
• Nx didn’t offer enough convenience or benefits for us to keep it

If Nx gets too involved in Next it gets in the way, and if it doesn’t then it doesn’t offer any value. At this point, we’ve seen both.

Nx worked with Angular:

• Stack is outdated and Nx offers a way to add new libraries and tooling
• Angular builds are slow and need the cloud offerings of Nx
• This convinced us that Nx could be helpful in other applications

Switching to yarn workspaces, we have a lot more control over each package and upgrading things. This flexibility gives us a lot and for a senior team, we feel much more comfortable with it.

Goodbye Nx, it was fun while it lasted.