Nx

Nx

@nx.dev

Smart Monorepos · Fast CI 🌐 https://nx.dev 💬 https://go.nx.dev/community 📺 https://youtube.com/@nxdevtools 🐙 https://github.com/nrwl/nx

1.8K followers13 following454 posts

View full thread
View full thread

Project graph creation got up to 60% faster on cold runs and up to 80% faster on warm runs in a large enterprise workspace. How much you gain depends on your repo and the machine it runs on.

View full thread

The Oxlint plugin we shipped in 23.2 now runs in batch mode by default. Nx starts a single Oxlint process for all projects, and each project still keeps its own result, logs and cache entry. On a workspace with 50 libraries, linting went from 16.5s to 3.0s.

When an AI agent runs Nx, it now gets the new summary output style by default. Nx prints the task counts and, for each failed task, the path to its full log. The agent reads a log file only when it needs the details, which keeps the token usage low.

Until now, nx affected worked at the project level. Change one spec file in a shared library and every project depending on it is affected too. 23.3 selects tasks by what they read, so that change only runs the test task of the project the spec file lives in.

Task-based affected is opt-in in 23.3 and we plan to make it the default in Nx 24: NX_LEGACY_AFFECTED=false nx affected -t test If a task shows up (or doesn't) and you're not sure why, add --explain. It lists the affected tasks and exits without running anything.

You can add Nx to an existing pnpm workspace without restructuring anything. Install nx at the root, add a small nx.json with your targetDefaults, and run tasks across every project with nx run-many. Caching and task ordering come from there.

View full thread

You can click on an agent to get machine details, like - the executed workflow steps - CPU and memory usage - processed tasks

Visually see how the CI run was distributed and easily spot problems. Like here you can see it is split into two chunks, something to investigate.

You can click on every task and see - inputs/outputs - logs - upstream and downstream dependencies - historical run data This gives the ability to quickly understand whether something is flaky or fails often, if runs got slower over time or has unexpected reads/writes.

Would you describe your CI as resilient? Nx Agents distribute CI tasks across multiple machines. Agents pull the next task from a shared pool as soon as they're free, so if a machine dies or a flaky test fails, another agent picks it up and CI keeps running. nx.dev/docs/featur...

Custom workspace ESLint rules are a good task to hand to your coding agent. Give it the link to the docs guide, and it scaffolds the plugin package and writes the rule for you. nx.dev/docs/kb/cus...

🚀 Nx 23.2 is out. - Oxlint & Oxfmt - Leaner CLI output for AI agents and CI - Caching across local clones & agent sandboxes - TUI status bar and VIM search - @angular.dev 22.1 - Expanded Vitest support And more. All the details 👇 nx.dev/blog/nx-23-...

Full end-to-end type safety across tech stacks is a dream for many developers. @craigory.dev makes it look easy. In his latest article, he shows how to achieve full-stack type safety in an Nx monorepo hosting a .NET WebAPI with a JavaScript frontend. nx.dev/blog/dotnet...

nx.devFull-Stack Type Safety Across Languages with @nx/dotnet | Nx BlogGenerate an OpenAPI document from a .NET API at build time, generate a TypeScript client from it, and let the Nx task graph keep the two in sync.

📣 Last call — tomorrow, 11am PT: Juri Strumpflohner will take you through why meta-harnesses are the next layer on top of your AI coding setup, and how to tell if one's worth adopting. Register (or grab the replay) → go.nx.dev/nx-webinar-...

go.nx.devNx Webinar - Why Everyone Is Building a Meta-Harness Right NowJoin our August webinar to learn why a shared meta-harness — not more personal workflow tweaks — is what decides whether AI agents make your whole org faster, not just one developer.

Everyone's hand-tuning their own AI harness right now, and it doesn't scale. We're one week out from hosting a webinar to cover the 3 shifts behind meta-harnesses: 1️⃣ manual→systematic 2️⃣ one harness→any harness 3️⃣ personal→organizational. Aug 4, 11am PT / 2pm ET. Sign up→ go.nx.dev/nx-webinar-...

go.nx.devNx Webinar - Why Everyone Is Building a Meta-Harness Right NowJoin our August webinar to learn why a shared meta-harness — not more personal workflow tweaks — is what decides whether AI agents make your whole org faster, not just one developer.

Harness engineering works great on one dev's machine – it falls apart the moment you try to scale it across a team. On Aug 4, we're hosting a webinar to break down the shift to meta-harnesses. Save your spot → go.nx.dev/nx-webinar-...

go.nx.devNx Webinar - Why Everyone Is Building a Meta-Harness Right NowJoin our August webinar to learn why a shared meta-harness — not more personal workflow tweaks — is what decides whether AI agents make your whole org faster, not just one developer.

Nx 23.1 is out 🎉. Some highlights: - Nx TUI now has mouse support (yes!) - More flexible targetDefaults - Performance reports after runs - Angular 22 - ... So much more. Check out the full blog post or chime into the thread below to see some excerpts: nx.dev/blog/nx-23-...

nx.devNx 23.1 Is Here: Per-Run Performance Reports, TypeScript 6, and Angular 22 | Nx BlogEverything that landed in Nx 23.1: a performance report at the end of every run, TypeScript 6, Angular 22 support, mouse support in the terminal UI, and more flexible target defaults.
View full thread

And we know a lot of you have been waiting for this: @angular.dev v22 support landed. We made sure migrations are smooth and the third-party ecosystem that integrates with both Nx and Angular is ready. Go upgrade!

Nx 23.1 is out 🎉. Some highlights: - Nx TUI now has mouse support (yes!) - More flexible targetDefaults - Performance reports after runs - Angular 22 - ... So much more. Check out the full blog post or chime into the thread below to see some excerpts: nx.dev/blog/nx-23-...

nx.devNx 23.1 Is Here: Per-Run Performance Reports, TypeScript 6, and Angular 22 | Nx BlogEverything that landed in Nx 23.1: a performance report at the end of every run, TypeScript 6, Angular 22 support, mouse support in the terminal UI, and more flexible target defaults.
View full thread

Defining defaults for your targets is crucial, and the ergonomics of how you do it matter a lot. With v23, we released the "spread" operator. Now we also allow you to filter your defaults to very specific projects or areas of your monorepo. See for yourself 👇

Also, full TypeScript v6 support (including migrations). And yeah, if you're wondering about TypeScript v7, you can use both side by side. Our guide has all the info: nx.dev/docs/techno...

Nx 23.1 is out 🎉. Some highlights: - Nx TUI now has mouse support (yes!) - More flexible targetDefaults - Performance reports after runs - Angular 22 - ... So much more. Check out the full blog post or chime into the thread below to see some excerpts: nx.dev/blog/nx-23-...

nx.devNx 23.1 Is Here: Per-Run Performance Reports, TypeScript 6, and Angular 22 | Nx BlogEverything that landed in Nx 23.1: a performance report at the end of every run, TypeScript 6, Angular 22 support, mouse support in the terminal UI, and more flexible target defaults.

The Nx TUI has mouse support now. Wait... what?? See it for yourself in action 👇

Last chance to register for AI ❤️ Monorepo Conf 2026 – Tues June 23rd. 9AM PT.

Nx reposted

Got access to @nx.dev Task Sandboxing today. Lets just say our caching inputs were NOT setup correctly 😅. Way to go Nx team, this feature is awesome.