👀

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.

Nx is 7x more memory efficient now. Yet, another feature we added to the Nx platform that really helped us track down how to improve Nx itself. - nx.dev/docs/guides/nx-cloud/… - nx.dev/blog/nx-22-7-release#…

Task sandboxing has been useful for us internally to find cache misconfiguration. This can result in both false-positive and false-negative cache hits/misses. We've been patching our plugins so Nx users get the right config OOTB. Looking forward to making this feature more widely available in the future.

Self-Healing CI is all about helping you waste less time debugging broken PRs. So the more we can trust to auto-apply, the better. That’s why we now analyze tasks and suggest the ones that can confidently be auto-applied. Read more in our blog post below.

We did the same on the nx.dev website. Thanks for the heads up @juristr ! isitagentready.com/nx.dev?ch…

We gotchu nx.dev/docs/getting-started/…

We reworked the Nx docs so the "getting started" experience is more streamlined and caters only to things everyone should learn. Nx is simpler than ever, and if you haven't tried it in a while I highly recommend taking a look again. Check it out! nx.dev/docs

I've been running CI monitor in Claude Code for two weeks, and it 100% of the time got my PR to green without my intervention. The only bottleneck now is getting human reviews once the PR is green. But I no longer need to use up mental capacity to babysit PRs.

Also ICYMI, we updated our information architecture for nx.dev/docs. We've grouped topics to general vs specific content, like general CI features vs specific Playwright features. It should be easier to navigate and find things.

We're working on a lot of cool things in 2026. I'm very excited about bring the benefits of Nx to synthetic monorepos. Definitely a lot of value to unlock here. Also, looking forward to less manual work to get that last mile to merged PRs using AI agents.

A little gift before we head out for the holidays: Nx 22.3 is live 🎁 🎉 Full @angular 21 support: zoneless, esbuild, and Vitest out of the box 🚀 Experimental tsgo compiler: test the future of @typescript 📝 @PrettierCode v3 compatibility Enjoy your holiday hacking!

We gave Claude Code the same feature request twice. ⏳ Polyrepo: 2 hours 🚀 Nx monorepo: 30 minutes Same app. Different setups. Wildly different results. Here's why your repo structure matters more than you think 🧵 (🔉 sound on 👇)

Tired of guessing why your CI is running out of memory? 🤔 Nx's new Agent Resource Usage view shows you exactly which tasks are consuming resources. No more blind guessing. Just data-driven decisions. 📊

Oh damn, Jason and myself will be overtaken by robots soon.

Nx 22 is out 🚀: 📊 Entirely new "nx graph" - finally works for large repos 🤖 nx configure-ai-agents tons of AI improvements ☕ First-class Maven & .NET support = true polyglot 💻 Improved Terminal UI, pnpm catalogs, and more @NxDevTools nx.dev/blog/nx-22-release