Free. Half-day. Online. June 23. AI ❤️ Monorepos Conf 2026 is here — talks from Kent C. Dodds, Jack Herrington, John Lindquist, Kiet Ho, Nicolas Beaussart, Brandon Roberts, and more. Plus: a live product launch you won't want to miss. Reserve your free ticket → monorepo.tools/conf

✨ @tan_stack built a code mode approach to agentic AI. Drastically lower tokens used, far higher accuracy. @jherr is walking through how it works. June 23. Register for free. monorepo.tools/conf/speaker/…

Devs often have to make trade-offs on the cache configuration: either ‘over-define’ and miss out on cache hits, or ‘under-defined’, which can lead to nightmare deployment scenarios like sending out an old build. Not anymore - try Sandboxing in Nx Cloud.

Dopey and I want to talk to you about Atomic Commits and polyrepos.

We're excited to have you join @kentcdodds!

Big thanks to my fellow Italian 🇮🇹 @giorgio_boa for: - creating Vite Module Federation in the first place 🤩 - putting together this Nx Vite MF example 🚀 🙇‍♂️ Give Giorgo a follow!! nx.dev/docs/technologies/mod…

Join us June 23rd for AI 💛 Monorepos Conf!

Angular v22 is now available 🥳 Here is a quick look at what's landing today: ✅ Signal Forms, Angular Aria & resource are officially STABLE ✅ OnPush change detection is now the default ✅ Template updates and more Read the full breakdown on the blog: 📰 goo.gle/angular-v22-blog Which of these updates is your favorite?

I use both dimensions as a starting point aligning with Nx best practices. While both have their value, for me, the scope/domain dimension is more important as it breaks the entire system in several decoupled pieces -> less cognitive load -> better maintainability -> more local changes, etc.

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've been working on something new and exciting for the past 6 months. The more progress we made, the more agent-related problems it solved. E.g., saw this in my feed the other day and thought: we sort of solved this one too. youtube.com/watch?v=y8OnoxKo…

Your build system's dashboards need to be as snappy as its terminal interface, don't you think?

Today we officially deprecated 4 packages that facilitated remote caching with Nx and different cloud providers: nx/s3-cache, nx/gcs-cache, nx/azure-cache and nx/shared-fs-cache. This is a proactive move to discourage a known attack vector in recent supply chain attacks: cache poisoning. This isn't related to Nx Cloud's remote caching which has built-in protection against poisoning. These plugins were used by teams who couldn't use Nx Cloud but wanted the speed benefits of distributed task caching. We published a CVE (CREEP CVE-2025-36852) last year against these packages to make it clear that they shouldn't be used for serious projects because of the inherent design flaw. But we still see the plugins used in irresponsible ways. Cyber attacks are ramping up, and are only going to get more effective as the tools the attackers use become more powerful. We're no longer compromising by providing tools that we know most users are using irresponsibly. The notice linked in the next tweet gives more details and recommendations.

We've published the full, detailed postmortem of the Nx Console compromise from Monday May 18th: nx.dev/blog/nx-console-v18-9…