Multi-version support compliance is coming to @NxDevTools v23, which means we will be able to plan atomic migrations of dependencies without a big-bang refactor when upgrading Nx. It's a major improvement as these upgrades can be tedious on some large workspaces.
We're considering integrating a merge queue, as our merge throughput has increased significantly with AI. I'd love to hear feedback from people with real-world experience. What tools have you used, and what are the pros and cons? We're managing a monorepo with trunk-based dev.
Increasing Nx parallelism doesn't always bring the performance benefits you think.
With tools that already parallelize internally (Vitest, Jest, esbuild...). You end up w/ threads competing for your CPUs, and runs become slower.
It’s almost impossible to maintain proper boundaries without more granular constraints. Today, we define boundaries at the project level, but files like *.spec.ts, *.story.ts, *.cy.ts, etc. shouldn’t be treated the same as src files.
